Automatic failover of a storage manager

ABSTRACT

An information management system implements a method for determining whether to initiate a failover of a storage manager in the system. Nodes in the system may be assigned as monitoring nodes configured to communicate with a storage manager. Furthermore, each monitoring node may be configured to transmit a status inquiry message to each other monitoring node, and each monitoring node may receive a status inquiry message from each other monitoring node. Each monitoring node may also generate a session message comprising status information, and a plurality of failover nodes may receive the generated session messages. A failover node may then determine whether a failover condition has occurred by applying a plurality of failover rules to the status information of the transmitted session message. Where the failover node determines that a failover condition has occurred, the failover node may activate another storage manager to take place of the presently assigned storage manager.

INCORPORATION BY REFERENCE TO ANY PRIORITY APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/175,259, filed on Feb. 12, 2021, and titled “AUTOMATIC FAILOVER OF ASTORAGE MANAGER,” Any and all applications, if any, for which a foreignor domestic priority claim is identified in the Application Data Sheetof the present application are hereby incorporated by reference in theirentireties under 37 CFR 1.57.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentand/or the patent disclosure as it appears in the United States Patentand Trademark Office patent file and/or records, but otherwise reservesall copyrights whatsoever.

BACKGROUND

Businesses recognize the commercial value of their data and seekreliable, cost-effective ways to protect the information stored on theircomputer networks while minimizing impact on productivity. A companymight back up critical computing systems such as databases, fileservers, web servers, virtual machines, and so on as part of a daily,weekly, or monthly maintenance schedule. The company may similarlyprotect computing systems used by its employees, such as those used byan accounting department, marketing department, engineering department,and so forth. Given the rapidly expanding volume of data undermanagement, companies also continue to seek innovative techniques formanaging data growth, for example by migrating data to lower-coststorage over time, reducing redundant data, pruning lower priority data,etc. Enterprises also increasingly view their stored data as a valuableasset and look for solutions that leverage their data. For instance,data analysis capabilities, information management, improved datapresentation and access features, and the like, are in increasingdemand.

In preserving primary data, the company may employ a storage managerthat manages information stored as primary data by one or more clientcomputing devices. Each of the client computing devices may back up theprimary data to one or more secondary computer devices. The company mayuse one or more networks, where each network includes one or more clientcomputing devices, and the client computing devices, storage manager,and secondary storage computing devices communicate using the one ormore networks.

Because the storage manager is responsible for managing the primary dataof the client computing devices, the storage manager may be backed up bya failover node, where the failover node takes on the jobs andresponsibilities of the storage manager when the storage managerexperiences a failure. The storage manager may experience a failure fora number reasons, such as a hardware failure, a power outage, corrupteddata, or any other number of reasons. However, there may be instanceswhere the storage manager appears to have failed, but has not actuallydone so. In these instances, reverting to the failover node may bepremature, and instantiating the failover node may introduce delays inthe operational status of the client computing devices and/or thesecondary storage computing devices that rely on the storage manager.

SUMMARY

To address these and other deficiencies, this disclosure describes aninformation management system that uses distributed computing techniquesto determine whether a storage manager has experienced an actual failureand, if so, whether another storage manager should be brought online toreplace the failed storage manager. In one embodiment, the informationmanagement system includes one or more networks of various devices andcomponents, such as one or more client computing devices, storagemanagers, and failover nodes. Each storage manager may be associatedwith a failover node, where the failover node is configured to determinewhether the associated storage manager has failed and, if so, todesignate another storage manager as the operational storage manager.

As there may be multiple storage managers in communication with thevarious client computing devices, a storage manager selected from themultiple storage managers may be designated as the “active” storagemanager. In this regard, the active storage manager is the storagemanager that is online, communicating with the various devices acrossthe one or more networks, such as the one or more client computingdevices, secondary storage computing devices, failover nodes, andoffline storage managers (e.g., a storage manager that is not currentlyactive but is able to receive and/or send communications across one ormore networks), and is managing the primary data and/or secondary dataof the information management system.

To ensure redundancy and operational continuation, the active storagemanager may be backed up to, and/or synchronized with, other storagemanagers. In this regard, the active storage manager may backup and/orsynchronize to other offline storage managers and/or failover nodes incommunication with the active storage manager. The backup of the activestorage manager may occur on a repeated, periodic basis, such as everyhour, every day, every other day, etc. The active storage manager maybackup or synchronize its data to a second, designated storage manager,to one or more of the offline storage managers, to one or more of thefailover nodes, or to all of the storage managers (failover ornon-failover) in communication with the active storage manager.

In the event of a storage manager failure, a determination is made as towhich storage manager should become the active storage manager. In oneembodiment, a failover node in communication with the previously, activestorage manager performs this determination. The failover node mayperform this determination by checking which of the other storagemanagers has a most recent backup or synchronization of a previously,active storage manager relative to the other storage managers that werebeing used for backup and/or synchronization. The failover node mayselect a previously offline storage manager to be the new, activestorage manager where the previously offline storage manager has a mostrecent backup of the previous active storage manager. Once online, thenew, active storage manager (e.g., the second active storage manager)may then communicate with the one or more client computing devices, theone or more secondary storage devices, and so forth, and inform each ofthese devices that the second active storage manager is the activestorage manager, and that these devices should accept instructions fromthe second active storage manager.

In determining whether the active storage manager has failed, variousdevices within the information management system may be designatedand/or assigned as a monitoring node. In one embodiment, a monitoringnode may be a device, such as a client computing device, storagemanager, secondary storage computing device, that is configured tocommunicate a status message to another monitoring node. In this regard,each monitoring node may be configured to communicate with each othermonitoring node. The monitoring nodes may be configured to communicate astatus message to each other monitoring node to determine whether theother monitoring node is reachable. The transmitting monitoring node maybe considered a source monitoring node, while the monitoring nodes towhom the status messages are sent may be considered destinationmonitoring nodes. The source monitoring node may wait a predeterminedtime period after each status message is sent to receive anacknowledgment message from a corresponding destination monitoring node.The source monitoring node aggregates the responses from the destinationmonitoring nodes into a session message that the source monitoring nodemay then send to the failover node. The session message may also includean identifier or flag to indicate whether an acknowledgment message wasnot received for a particular monitoring node (e.g., the particularmonitoring node was unresponsive).

The failover node then collects the session messages from each of themonitoring nodes. The failover node may maintain a data structure thatlists and/or updates the status of each of the monitoring nodes based onthe collected session messages. For example, the data structure may be atwo-dimensional table, and the intersections within the table store avalue that indicates whether a source monitoring node received anacknowledgment from a destination monitoring node. The failover node maythen communicate this data structure as one or more session messages toeach of the monitoring nodes, such that each monitoring node is providedwith a copy of the data structure.

The failover node may reference the node status data structure indetermining whether the active failover node has actually failed. Forexample, the failover node may periodically send a status message to theactive storage manager to ensure that the active storage manager isonline. In this example, the failover node may fail to receive anacknowledgement message from the active storage manager within apredetermined time period. This failure may signal to the failover nodethat the active storage manager has failed. To confirm whether theactive storage manager has failed, the failover node may reference thenode status data structure to determine whether other monitoring nodeshave received acknowledgement messages from the active storage manager.The failover node may be further configured with one or more failoverrules that define or specify the circumstances under which the failovernode may confirm that the active storage manager has failed. Thefailover node may execute the rules using the node status values fromthe node status data structure to determine and/or confirm whether thestorage manager has actually failed. Where the storage manager hasactually failed, the failover node may enter a failover state, where thefailover node then determines which of the storage managers then becomesthe active storage manager. The failover node may select the new, activestorage manager from the other storage managers based on one or morefactors including, but not limited to, geographical proximity to thefailed storage manager, synchronization or backup time, a numerical orpriority identifier, or any other factor and/or combination thereof.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram illustrating an exemplary informationmanagement system.

FIG. 1B is a detailed view of a primary storage device, a secondarystorage device, and some examples of primary data and secondary copydata.

FIG. 1C is a block diagram of an exemplary information management systemincluding a storage manager, one or more data agents, and one or moremedia agents.

FIG. 1D is a block diagram illustrating a scalable informationmanagement system.

FIG. 1E illustrates certain secondary copy operations according to anexemplary storage policy.

FIGS. 1F-1H are block diagrams illustrating suitable data structuresthat may be employed by the information management system.

FIG. 2A illustrates a system and technique for synchronizing primarydata to a destination such as a failover site using secondary copy data.

FIG. 2B illustrates an information management system architectureincorporating use of a network file system (NFS) protocol forcommunicating between the primary and secondary storage subsystems.

FIG. 2C is a block diagram of an example of a highly scalable manageddata pool architecture.

FIG. 3A illustrates an information management system configured toperform automatic failover of a storage manager, in accordance with anexample embodiment.

FIG. 3B illustrates the information management system of FIG. 3A, whereone or more devices have been designated as monitoring nodes, inaccordance with an example embodiment.

FIG. 4 illustrates communication pathways of a selected group ofmonitoring nodes illustrated in FIG. 3B, in accordance with an exampleembodiment.

FIG. 5 illustrates a client computing device of the informationmanagement system of FIG. 3A, in accordance with an example embodiment.

FIG. 6 illustrates a storage manager of the information managementsystem of FIG. 3A, in accordance with an example embodiment.

FIG. 7 illustrates a failover node of the information management systemof FIG. 3A, in accordance with an example embodiment.

FIG. 8 illustrates a messaging diagram for updating monitoring nodestatuses of the information management system of FIG. 3A, in accordancewith an example embodiment.

FIGS. 9A-9B illustrate a method, in accordance with an exampleembodiment, for updating node statuses within the information managementsystem of FIG. 3A and determining whether to enter a failover state ofan active storage manager.

FIGS. 10A-10B illustrate a method, in accordance with an exampleembodiment, for activating a failover node of the information managementsystem illustrated in FIG. 3A.

DETAILED DESCRIPTION

Detailed descriptions and examples of systems and methods according toone or more illustrative embodiments may be found in the section titled“Automatic Failover of a Storage Manager,” as well as in the sectiontitled Example Embodiments, and also in FIGS. 3A-10B herein.Furthermore, components and functionality for the disclosed recoverymanager may be configured and/or incorporated into informationmanagement systems such as those described herein in FIGS. 1A-1H and2A-2C.

Various embodiments described herein are intimately tied to, enabled by,and would not exist except for, computer technology. For example, thetransference of backup jobs from the storage manager to the recoverymanager described herein, in reference to various embodiments, cannotreasonably be performed by humans alone, without the computer technologyupon which they are implemented.

Information Management System Overview

With the increasing importance of protecting and leveraging data,organizations simply cannot risk losing critical data. Moreover, runawaydata growth and other modern realities make protecting and managing dataincreasingly difficult. There is therefore a need for efficient,powerful, and user-friendly solutions for protecting and managing dataand for smart and efficient management of data storage. Depending on thesize of the organization, there may be many data production sourceswhich are under the purview of tens, hundreds, or even thousands ofindividuals. In the past, individuals were sometimes responsible formanaging and protecting their own data, and a patchwork of hardware andsoftware point solutions may have been used in any given organization.These solutions were often provided by different vendors and had limitedor no interoperability. Certain embodiments described herein addressthese and other shortcomings of prior approaches by implementingscalable, unified, organization-wide information management, includingdata storage management.

FIG. 1A shows one such information management system 100 (or “system100”), which generally includes combinations of hardware and softwareconfigured to protect and manage data and metadata that are generatedand used by computing devices in system 100. System 100 may be referredto in some embodiments as a “storage management system” or a “datastorage management system.” System 100 performs information managementoperations, some of which may be referred to as “storage operations” or“data storage operations,” to protect and manage the data residing inand/or managed by system 100. The organization that employs system 100may be a corporation or other business entity, non-profit organization,educational institution, household, governmental agency, or the like.

Generally, the systems and associated components described herein may becompatible with and/or provide some or all of the functionality of thesystems and corresponding components described in one or more of thefollowing U.S. patents/publications and patent applications assigned toCommvault Systems, Inc., each of which is hereby incorporated byreference in its entirety herein:

-   -   U.S. Pat. No. 7,035,880, entitled “Modular Backup and Retrieval        System Used in Conjunction With a Storage Area Network”;    -   U.S. Pat. No. 7,107,298, entitled “System And Method For        Archiving Objects In An Information Store”;    -   U.S. Pat. No. 7,246,207, entitled “System and Method for        Dynamically Performing Storage Operations in a Computer        Network”;    -   U.S. Pat. No. 7,315,923, entitled “System And Method For        Combining Data Streams In Pipelined Storage Operations In A        Storage Network”;    -   U.S. Pat. No. 7,343,453, entitled “Hierarchical Systems and        Methods for Providing a Unified View of Storage Information”;    -   U.S. Pat. No. 7,395,282, entitled “Hierarchical Backup and        Retrieval System”;    -   U.S. Pat. No. 7,529,782, entitled “System and Methods for        Performing a Snapshot and for Restoring Data”;    -   U.S. Pat. No. 7,617,262, entitled “System and Methods for        Monitoring Application Data in a Data Replication System”;    -   U.S. Pat. No. 7,734,669, entitled “Managing Copies Of Data”;    -   U.S. Pat. No. 7,747,579, entitled “Metabase for Facilitating        Data Classification”;    -   U.S. Pat. No. 8,156,086, entitled “Systems And Methods For        Stored Data Verification”;    -   U.S. Pat. No. 8,170,995, entitled “Method and System for Offline        Indexing of Content and Classifying Stored Data”;    -   U.S. Pat. No. 8,230,195, entitled “System And Method For        Performing Auxiliary Storage Operations”;    -   U.S. Pat. No. 8,285,681, entitled “Data Object Store and Server        for a Cloud Storage Environment, Including Data Deduplication        and Data Management Across Multiple Cloud Storage Sites”;    -   U.S. Pat. No. 8,307,177, entitled “Systems And Methods For        Management Of Virtualization Data”;    -   U.S. Pat. No. 8,364,652, entitled “Content-Aligned, Block-Based        Deduplication”;    -   U.S. Pat. No. 8,578,120, entitled “Block-Level Single        Instancing”;    -   U.S. Pat. No. 8,954,446, entitled “Client-Side Repository in a        Networked Deduplicated Storage System”;    -   U.S. Pat. No. 9,020,900, entitled “Distributed Deduplicated        Storage System”;    -   U.S. Pat. No. 9,098,495, entitled “Application-Aware and Remote        Single Instance Data Management”;    -   U.S. Pat. No. 9,239,687, entitled “Systems and Methods for        Retaining and Using Data Block Signatures in Data Protection        Operations”;    -   U.S. Pat. Pub. No. 2006/0224846, entitled “System and Method to        Support Single Instance Storage Operations” (now abandoned);    -   U.S. Pat. Pub. No. 2014/0201170, entitled “High Availability        Distributed Deduplicated Storage System”, now U.S. Pat. No.        9,633,033;    -   U.S. Pat. Pub. No. 2016/0041880 A1, entitled “Efficient        Application Recovery in an Information Management System Based        on a Pseudo-Storage-Device Driver”, now U.S. Pat. No. 9,852,026;    -   U.S. patent application Ser. No. 14/721,971, entitled        “Replication Using Deduplicated Secondary Copy Data” (applicant        matter no. 100.422.US1.145; attorney docket no. COMMV.252A),        published as U.S. Pat. Pub. No. 2016/0350391;    -   U.S. patent application Ser. No. 14/805,615, entitled “Browse        and Restore for Block-Level Backups” (applicant matter no.        100.434.US1.20; attorney docket no. 060692-8141.US00), now U.S.        Pat. No. 9,766,825.    -   U.S. Provisional Patent Application No. 62/265,339 entitled        “Live Synchronization and Management of Virtual Machines across        Computing and Virtualization Platforms and Using Live        Synchronization to Support Disaster Recovery” (applicant docket        no. 100.487.USP1.160; attorney docket no. COMMV.277PR), to which        U.S. patent application Ser. No. 15/365,756 claims priority (now        U.S. Pat. No. 10,228,962);    -   U.S. Provisional Patent Application No. 62/273,286 entitled        “Redundant and Robust Distributed Deduplication Data Storage        System” (applicant docket no. 100.489.USP1.135; attorney docket        no. COMMV.279PR), to which U.S. patent application Ser. No.        15/299,254 (now U.S. Pat. No. 10,310,953), Ser. No. 15/299,281        (published as U.S. Pat Pub. 2017-0192868), Ser. No. 15/299,291        (now U.S. Pat. No. 10,138,729), Ser. No. 15/299,298 (now U.S.        Pat. No. 10,592,357), Ser. No. 15/299,299 (published as U.S.        Pat. Pub. US 2017-0193003), and Ser. No. 15/299,280 (now U.S.        Pat. No. 10,061,663) all claim priority;    -   U.S. Provisional Patent Application No. 62/294,920, entitled        “Data Protection Operations Based on Network Path Information”        (applicant docket no. 100.497.USP1.105; attorney docket no.        COMMV.283PR), to which U.S. patent application Ser. No.        15/283,033 claims priority (published as U.S. Pat. Pub. No.        2017/0235647 (now abandoned));    -   U.S. Provisional Patent Application No. 62/297,057 entitled        “Data Restoration Operations Based on Network Path Information”        (applicant docket no. 100.498.USP1.105; attorney docket no.        COMMV.284PR), to which U.S. patent application Ser. No.        15/286,403 claims priority (published as U.S. Pat. Pub. No.        2017/0242871); and    -   U.S. Provisional Patent Application No. 62/387,384, entitled        “Application-Level Live Synchronization Across Computing        Platforms Including Synchronizing Co-Resident Applications To        Disparate Standby Destinations And Selectively Synchronizing        Some Applications and Not Others” (applicant docket no.        100.500.USP1.105; attorney docket no. COMMV.286PR), to which        U.S. patent application Ser. No. 15/369,676 claims priority (now        U.S. Pat. No. 10,387,266).

System 100 includes computing devices and computing technologies. Forinstance, system 100 can include one or more client computing devices102 and secondary storage computing devices 106, as well as storagemanager 140 or a host computing device for it. Computing devices caninclude, without limitation, one or more: workstations, personalcomputers, desktop computers, or other types of generally fixedcomputing systems such as mainframe computers, servers, andminicomputers. Other computing devices can include mobile or portablecomputing devices, such as one or more laptops, tablet computers,personal data assistants, mobile phones (such as smartphones), and othermobile or portable computing devices such as embedded computers, set topboxes, vehicle-mounted devices, wearable computers, etc. Servers caninclude mail servers, file servers, database servers, virtual machineservers, and web servers. Any given computing device comprises one ormore processors (e.g., CPU and/or single-core or multi-core processors),as well as corresponding non-transitory computer memory (e.g.,random-access memory (RAM)) for storing computer programs which are tobe executed by the one or more processors. Other computer memory formass storage of data may be packaged/configured with the computingdevice (e.g., an internal hard disk) and/or may be external andaccessible by the computing device (e.g., network-attached storage, astorage array, etc.). In some cases, a computing device includes cloudcomputing resources, which may be implemented as virtual machines. Forinstance, one or more virtual machines may be provided to theorganization by a third-party cloud service vendor.

In some embodiments, computing devices can include one or more virtualmachine(s) running on a physical host computing device (or “hostmachine”) operated by the organization. As one example, the organizationmay use one virtual machine as a database server and another virtualmachine as a mail server, both virtual machines operating on the samehost machine. A Virtual machine (“VM”) is a software implementation of acomputer that does not physically exist and is instead instantiated inan operating system of a physical computer (or host machine) to enableapplications to execute within the VM's environment, i.e., a VM emulatesa physical computer. A VM includes an operating system and associatedvirtual resources, such as computer memory and processor(s). Ahypervisor operates between the VM and the hardware of the physical hostmachine and is generally responsible for creating and running the VMs.Hypervisors are also known in the art as virtual machine monitors or avirtual machine managers or “VMMs”, and may be implemented in software,firmware, and/or specialized hardware installed on the host machine.Examples of hypervisors include ESX Server, by VMware, Inc. of PaloAlto, Calif.; Microsoft Virtual Server and Microsoft Windows ServerHyper-V, both by Microsoft Corporation of Redmond, Wash.; Sun xVM byOracle America Inc. of Santa Clara, Calif.; and Xen by Citrix Systems,Santa Clara, Calif. The hypervisor provides resources to each virtualoperating system such as a virtual processor, virtual memory, a virtualnetwork device, and a virtual disk. Each virtual machine has one or moreassociated virtual disks. The hypervisor typically stores the data ofvirtual disks in files on the file system of the physical host machine,called virtual machine disk files (“VMDK” in VMware lingo) or virtualhard disk image files (in Microsoft lingo). For example, VMware's ESXServer provides the Virtual Machine File System (VMFS) for the storageof virtual machine disk files. A virtual machine reads data from andwrites data to its virtual disk much the way that a physical machinereads data from and writes data to a physical disk. Examples oftechniques for implementing information management in a cloud computingenvironment are described in U.S. Pat. No. 8,285,681. Examples oftechniques for implementing information management in a virtualizedcomputing environment are described in U.S. Pat. No. 8,307,177.

Information management system 100 can also include electronic datastorage devices, generally used for mass storage of data, including,e.g., primary storage devices 104 and secondary storage devices 108.Storage devices can generally be of any suitable type including, withoutlimitation, disk drives, storage arrays (e.g., storage-area network(SAN) and/or network-attached storage (NAS) technology), semiconductormemory (e.g., solid state storage devices), network attached storage(NAS) devices, tape libraries, or other magnetic, non-tape storagedevices, optical media storage devices, combinations of the same, etc.In some embodiments, storage devices form part of a distributed filesystem. In some cases, storage devices are provided in a cloud storageenvironment (e.g., a private cloud or one operated by a third-partyvendor), whether for primary data or secondary copies or both.

Depending on context, the term “information management system” can referto generally all of the illustrated hardware and software components inFIG. 1C, or the term may refer to only a subset of the illustratedcomponents. For instance, in some cases, system 100 generally refers toa combination of specialized components used to protect, move, manage,manipulate, analyze, and/or process data and metadata generated byclient computing devices 102. However, system 100 in some cases does notinclude the underlying components that generate and/or store primarydata 112, such as the client computing devices 102 themselves, and theprimary storage devices 104. Likewise secondary storage devices 108(e.g., a third-party provided cloud storage environment) may not be partof system 100. As an example, “information management system” or“storage management system” may sometimes refer to one or more of thefollowing components, which will be described in further detail below:storage manager, data agent, and media agent.

One or more client computing devices 102 may be part of system 100, eachclient computing device 102 having an operating system and at least oneapplication 110 and one or more accompanying data agents executingthereon; and associated with one or more primary storage devices 104storing primary data 112. Client computing device(s) 102 and primarystorage devices 104 may generally be referred to in some cases asprimary storage subsystem 117.

Client Computing Devices, Clients, and Subclients

Typically, a variety of sources in an organization produce data to beprotected and managed. As just one illustrative example, in a corporateenvironment such data sources can be employee workstations and companyservers such as a mail server, a web server, a database server, atransaction server, or the like. In system 100, data generation sourcesinclude one or more client computing devices 102. A computing devicethat has a data agent 142 installed and operating on it is generallyreferred to as a “client computing device” 102, and may include any typeof computing device, without limitation. A client computing device 102may be associated with one or more users and/or user accounts.

A “client” is a logical component of information management system 100,which may represent a logical grouping of one or more data agentsinstalled on a client computing device 102. Storage manager 140recognizes a client as a component of system 100, and in someembodiments, may automatically create a client component the first timea data agent 142 is installed on a client computing device 102. Becausedata generated by executable component(s) 110 is tracked by theassociated data agent 142 so that it may be properly protected in system100, a client may be said to generate data and to store the generateddata to primary storage, such as primary storage device 104. However,the terms “client” and “client computing device” as used herein do notimply that a client computing device 102 is necessarily configured inthe client/server sense relative to another computing device such as amail server, or that a client computing device 102 cannot be a server inits own right. As just a few examples, a client computing device 102 canbe and/or include mail servers, file servers, database servers, virtualmachine servers, and/or web servers.

Each client computing device 102 may have application(s) 110 executingthereon which generate and manipulate the data that is to be protectedfrom loss and managed in system 100. Applications 110 generallyfacilitate the operations of an organization, and can include, withoutlimitation, mail server applications (e.g., Microsoft Exchange Server),file system applications, mail client applications (e.g., MicrosoftExchange Client), database applications or database management systems(e.g., SQL, Oracle, SAP, Lotus Notes Database), word processingapplications (e.g., Microsoft Word), spreadsheet applications, financialapplications, presentation applications, graphics and/or videoapplications, browser applications, mobile applications, entertainmentapplications, and so on. Each application 110 may be accompanied by anapplication-specific data agent 142, though not all data agents 142 areapplication-specific or associated with only application. A file managerapplication, e.g., Microsoft Windows Explorer, may be considered anapplication 110 and may be accompanied by its own data agent 142. Clientcomputing devices 102 can have at least one operating system (e.g.,Microsoft Windows, Mac OS X, iOS, IBM z/OS, Linux, other Unix-basedoperating systems, etc.) installed thereon, which may support or hostone or more file systems and other applications 110. In someembodiments, a virtual machine that executes on a host client computingdevice 102 may be considered an application 110 and may be accompaniedby a specific data agent 142 (e.g., virtual server data agent).

Client computing devices 102 and other components in system 100 can beconnected to one another via one or more electronic communicationpathways 114. For example, a first communication pathway 114 maycommunicatively couple client computing device 102 and secondary storagecomputing device 106; a second communication pathway 114 maycommunicatively couple storage manager 140 and client computing device102; and a third communication pathway 114 may communicatively couplestorage manager 140 and secondary storage computing device 106, etc.(see, e.g., FIG. 1A and FIG. 1C). A communication pathway 114 caninclude one or more networks or other connection types including one ormore of the following, without limitation: the Internet, a wide areanetwork (WAN), a local area network (LAN), a Storage Area Network (SAN),a Fibre Channel (FC) connection, a Small Computer System Interface(SCSI) connection, a virtual private network (VPN), a token ring orTCP/IP based network, an intranet network, a point-to-point link, acellular network, a wireless data transmission system, a two-way cablesystem, an interactive kiosk network, a satellite network, a broadbandnetwork, a baseband network, a neural network, a mesh network, an ad hocnetwork, other appropriate computer or telecommunications networks,combinations of the same or the like. Communication pathways 114 in somecases may also include application programming interfaces (APIs)including, e.g., cloud service provider APIs, virtual machine managementAPIs, and hosted service provider APIs. The underlying infrastructure ofcommunication pathways 114 may be wired and/or wireless, analog and/ordigital, or any combination thereof; and the facilities used may beprivate, public, third-party provided, or any combination thereof,without limitation.

A “subclient” is a logical grouping of all or part of a client's primarydata 112. In general, a subclient may be defined according to how thesubclient data is to be protected as a unit in system 100. For example,a subclient may be associated with a certain storage policy. A givenclient may thus comprise several subclients, each subclient associatedwith a different storage policy. For example, some files may form afirst subclient that requires compression and deduplication and isassociated with a first storage policy. Other files of the client mayform a second subclient that requires a different retention schedule aswell as encryption, and may be associated with a different, secondstorage policy. As a result, though the primary data may be generated bythe same application 110 and may belong to one given client, portions ofthe data may be assigned to different subclients for distinct treatmentby system 100. More detail on subclients is given in regard to storagepolicies below.

Primary Data and Exemplary Primary Storage Devices

Primary data 112 is generally production data or “live” data generatedby the operating system and/or applications 110 executing on clientcomputing device 102. Primary data 112 is generally stored on primarystorage device(s) 104 and is organized via a file system operating onthe client computing device 102. Thus, client computing device(s) 102and corresponding applications 110 may create, access, modify, write,delete, and otherwise use primary data 112. Primary data 112 isgenerally in the native format of the source application 110. Primarydata 112 is an initial or first stored body of data generated by thesource application 110. Primary data 112 in some cases is createdsubstantially directly from data generated by the corresponding sourceapplication 110. It can be useful in performing certain tasks toorganize primary data 112 into units of different granularities. Ingeneral, primary data 112 can include files, directories, file systemvolumes, data blocks, extents, or any other hierarchies or organizationsof data objects. As used herein, a “data object” can refer to (i) anyfile that is currently addressable by a file system or that waspreviously addressable by the file system (e.g., an archive file),and/or to (ii) a subset of such a file (e.g., a data block, an extent,etc.). Primary data 112 may include structured data (e.g., databasefiles), unstructured data (e.g., documents), and/or semi-structureddata. See, e.g., FIG. 1B.

It can also be useful in performing certain functions of system 100 toaccess and modify metadata within primary data 112. Metadata generallyincludes information about data objects and/or characteristicsassociated with the data objects. For simplicity herein, it is to beunderstood that, unless expressly stated otherwise, any reference toprimary data 112 generally also includes its associated metadata, butreferences to metadata generally do not include the primary data.Metadata can include, without limitation, one or more of the following:the data owner (e.g., the client or user that generates the data), thelast modified time (e.g., the time of the most recent modification ofthe data object), a data object name (e.g., a file name), a data objectsize (e.g., a number of bytes of data), information about the content(e.g., an indication as to the existence of a particular search term),user-supplied tags, to/from information for email (e.g., an emailsender, recipient, etc.), creation date, file type (e.g., format orapplication type), last accessed time, application type (e.g., type ofapplication that generated the data object), location/network (e.g., acurrent, past or future location of the data object and network pathwaysto/from the data object), geographic location (e.g., GPS coordinates),frequency of change (e.g., a period in which the data object ismodified), business unit (e.g., a group or department that generates,manages or is otherwise associated with the data object), aginginformation (e.g., a schedule, such as a time period, in which the dataobject is migrated to secondary or long term storage), boot sectors,partition layouts, file location within a file folder directorystructure, user permissions, owners, groups, access control lists(ACLs), system metadata (e.g., registry information), combinations ofthe same or other similar information related to the data object. Inaddition to metadata generated by or related to file systems andoperating systems, some applications 110 and/or other components ofsystem 100 maintain indices of metadata for data objects, e.g., metadataassociated with individual email messages. The use of metadata toperform classification and other functions is described in greaterdetail below.

Primary storage devices 104 storing primary data 112 may be relativelyfast and/or expensive technology (e.g., flash storage, a disk drive, ahard-disk storage array, solid state memory, etc.), typically to supporthigh-performance live production environments. Primary data 112 may behighly changeable and/or may be intended for relatively short termretention (e.g., hours, days, or weeks). According to some embodiments,client computing device 102 can access primary data 112 stored inprimary storage device 104 by making conventional file system calls viathe operating system. Each client computing device 102 is generallyassociated with and/or in communication with one or more primary storagedevices 104 storing corresponding primary data 112. A client computingdevice 102 is said to be associated with or in communication with aparticular primary storage device 104 if it is capable of one or moreof: routing and/or storing data (e.g., primary data 112) to the primarystorage device 104, coordinating the routing and/or storing of data tothe primary storage device 104, retrieving data from the primary storagedevice 104, coordinating the retrieval of data from the primary storagedevice 104, and modifying and/or deleting data in the primary storagedevice 104. Thus, a client computing device 102 may be said to accessdata stored in an associated storage device 104.

Primary storage device 104 may be dedicated or shared. In some cases,each primary storage device 104 is dedicated to an associated clientcomputing device 102, e.g., a local disk drive. In other cases, one ormore primary storage devices 104 can be shared by multiple clientcomputing devices 102, e.g., via a local network, in a cloud storageimplementation, etc. As one example, primary storage device 104 can be astorage array shared by a group of client computing devices 102, such asEMC Clariion, EMC Symmetrix, EMC Celerra, Dell EqualLogic, IBM XIV,NetApp FAS, HP EVA, and HP 3PAR.

System 100 may also include hosted services (not shown), which may behosted in some cases by an entity other than the organization thatemploys the other components of system 100. For instance, the hostedservices may be provided by online service providers. Such serviceproviders can provide social networking services, hosted email services,or hosted productivity applications or other hosted applications such assoftware-as-a-service (SaaS), platform-as-a-service (PaaS), applicationservice providers (ASPs), cloud services, or other mechanisms fordelivering functionality via a network. As it services users, eachhosted service may generate additional data and metadata, which may bemanaged by system 100, e.g., as primary data 112. In some cases, thehosted services may be accessed using one of the applications 110. As anexample, a hosted mail service may be accessed via browser running on aclient computing device 102.

Secondary Copies and Exemplary Secondary Storage Devices

Primary data 112 stored on primary storage devices 104 may becompromised in some cases, such as when an employee deliberately oraccidentally deletes or overwrites primary data 112. Or primary storagedevices 104 can be damaged, lost, or otherwise corrupted. For recoveryand/or regulatory compliance purposes, it is therefore useful togenerate and maintain copies of primary data 112. Accordingly, system100 includes one or more secondary storage computing devices 106 and oneor more secondary storage devices 108 configured to create and store oneor more secondary copies 116 of primary data 112 including itsassociated metadata. The secondary storage computing devices 106 and thesecondary storage devices 108 may be referred to as secondary storagesubsystem 118.

Secondary copies 116 can help in search and analysis efforts and meetother information management goals as well, such as: restoring dataand/or metadata if an original version is lost (e.g., by deletion,corruption, or disaster); allowing point-in-time recovery; complyingwith regulatory data retention and electronic discovery (e-discovery)requirements; reducing utilized storage capacity in the productionsystem and/or in secondary storage; facilitating organization and searchof data; improving user access to data files across multiple computingdevices and/or hosted services; and implementing data retention andpruning policies.

A secondary copy 116 can comprise a separate stored copy of data that isderived from one or more earlier-created stored copies (e.g., derivedfrom primary data 112 or from another secondary copy 116). Secondarycopies 116 can include point-in-time data, and may be intended forrelatively long-term retention before some or all of the data is movedto other storage or discarded. In some cases, a secondary copy 116 maybe in a different storage device than other previously stored copies;and/or may be remote from other previously stored copies. Secondarycopies 116 can be stored in the same storage device as primary data 112.For example, a disk array capable of performing hardware snapshotsstores primary data 112 and creates and stores hardware snapshots of theprimary data 112 as secondary copies 116. Secondary copies 116 may bestored in relatively slow and/or lower cost storage (e.g., magnetictape). A secondary copy 116 may be stored in a backup or archive format,or in some other format different from the native source applicationformat or other format of primary data 112.

Secondary storage computing devices 106 may index secondary copies 116(e.g., using a media agent 144), enabling users to browse and restore ata later time and further enabling the lifecycle management of theindexed data. After creation of a secondary copy 116 that representscertain primary data 112, a pointer or other location indicia (e.g., astub) may be placed in primary data 112, or be otherwise associated withprimary data 112, to indicate the current location of a particularsecondary copy 116. Since an instance of a data object or metadata inprimary data 112 may change over time as it is modified by application110 (or hosted service or the operating system), system 100 may createand manage multiple secondary copies 116 of a particular data object ormetadata, each copy representing the state of the data object in primarydata 112 at a particular point in time. Moreover, since an instance of adata object in primary data 112 may eventually be deleted from primarystorage device 104 and the file system, system 100 may continue tomanage point-in-time representations of that data object, even thoughthe instance in primary data 112 no longer exists. For virtual machines,the operating system and other applications 110 of client computingdevice(s) 102 may execute within or under the management ofvirtualization software (e.g., a VMM), and the primary storage device(s)104 may comprise a virtual disk created on a physical storage device.System 100 may create secondary copies 116 of the files or other dataobjects in a virtual disk file and/or secondary copies 116 of the entirevirtual disk file itself (e.g., of an entire .vmdk file).

Secondary copies 116 are distinguishable from corresponding primary data112. First, secondary copies 116 can be stored in a different formatfrom primary data 112 (e.g., backup, archive, or other non-nativeformat). For this or other reasons, secondary copies 116 may not bedirectly usable by applications 110 or client computing device 102(e.g., via standard system calls or otherwise) without modification,processing, or other intervention by system 100 which may be referred toas “restore” operations. Secondary copies 116 may have been processed bydata agent 142 and/or media agent 144 in the course of being created(e.g., compression, deduplication, encryption, integrity markers,indexing, formatting, application-aware metadata, etc.), and thussecondary copy 116 may represent source primary data 112 withoutnecessarily being exactly identical to the source.

Second, secondary copies 116 may be stored on a secondary storage device108 that is inaccessible to application 110 running on client computingdevice 102 and/or hosted service. Some secondary copies 116 may be“offline copies,” in that they are not readily available (e.g., notmounted to tape or disk). Offline copies can include copies of data thatsystem 100 can access without human intervention (e.g., tapes within anautomated tape library, but not yet mounted in a drive), and copies thatthe system 100 can access only with some human intervention (e.g., tapeslocated at an offsite storage site).

Using Intermediate Devices for Creating Secondary Copies—SecondaryStorage Computing Devices

Creating secondary copies can be challenging when hundreds or thousandsof client computing devices 102 continually generate large volumes ofprimary data 112 to be protected. Also, there can be significantoverhead involved in the creation of secondary copies 116. Moreover,specialized programmed intelligence and/or hardware capability isgenerally needed for accessing and interacting with secondary storagedevices 108. Client computing devices 102 may interact directly with asecondary storage device 108 to create secondary copies 116, but in viewof the factors described above, this approach can negatively impact theability of client computing device 102 to serve/service application 110and produce primary data 112. Further, any given client computing device102 may not be optimized for interaction with certain secondary storagedevices 108.

Thus, system 100 may include one or more software and/or hardwarecomponents which generally act as intermediaries between clientcomputing devices 102 (that generate primary data 112) and secondarystorage devices 108 (that store secondary copies 116). In addition tooff-loading certain responsibilities from client computing devices 102,these intermediate components provide other benefits. For instance, asdiscussed further below with respect to FIG. 1D, distributing some ofthe work involved in creating secondary copies 116 can enhancescalability and improve system performance. For instance, usingspecialized secondary storage computing devices 106 and media agents 144for interfacing with secondary storage devices 108 and/or for performingcertain data processing operations can greatly improve the speed withwhich system 100 performs information management operations and can alsoimprove the capacity of the system to handle large numbers of suchoperations, while reducing the computational load on the productionenvironment of client computing devices 102. The intermediate componentscan include one or more secondary storage computing devices 106 as shownin FIG. 1A and/or one or more media agents 144. Media agents arediscussed further below (e.g., with respect to FIGS. 1C-1E). Thesespecial-purpose components of system 100 comprise specialized programmedintelligence and/or hardware capability for writing to, reading from,instructing, communicating with, or otherwise interacting with secondarystorage devices 108.

Secondary storage computing device(s) 106 can comprise any of thecomputing devices described above, without limitation. In some cases,secondary storage computing device(s) 106 also include specializedhardware componentry and/or software intelligence (e.g., specializedinterfaces) for interacting with certain secondary storage device(s) 108with which they may be specially associated.

To create a secondary copy 116 involving the copying of data fromprimary storage subsystem 117 to secondary storage subsystem 118, clientcomputing device 102 may communicate the primary data 112 to be copied(or a processed version thereof generated by a data agent 142) to thedesignated secondary storage computing device 106, via a communicationpathway 114. Secondary storage computing device 106 in turn may furtherprocess and convey the data or a processed version thereof to secondarystorage device 108. One or more secondary copies 116 may be created fromexisting secondary copies 116, such as in the case of an auxiliary copyoperation, described further below.

Exemplary Primary Data and an Exemplary Secondary Copy

FIG. 16 is a detailed view of some specific examples of primary datastored on primary storage device(s) 104 and secondary copy data storedon secondary storage device(s) 108, with other components of the systemremoved for the purposes of illustration. Stored on primary storagedevice(s) 104 are primary data 112 objects including word processingdocuments 119A-B, spreadsheets 120, presentation documents 122, videofiles 124, image files 126, email mailboxes 128 (and corresponding emailmessages 129A-C), HTML/XML or other types of markup language files 130,databases 132 and corresponding tables or other data structures133A-133C. Some or all primary data 112 objects are associated withcorresponding metadata (e.g., “Meta1-11”), which may include file systemmetadata and/or application-specific metadata. Stored on the secondarystorage device(s) 108 are secondary copy 116 data objects 134A-C whichmay include copies of or may otherwise represent corresponding primarydata 112.

Secondary copy data objects 134A-C can individually represent more thanone primary data object. For example, secondary copy data object 134Arepresents three separate primary data objects 133C, 122, and 129C(represented as 133C′, 122′, and 129C′, respectively, and accompanied bycorresponding metadata Meta11, Meta3, and Meta8, respectively).Moreover, as indicated by the prime mark (′), secondary storagecomputing devices 106 or other components in secondary storage subsystem118 may process the data received from primary storage subsystem 117 andstore a secondary copy including a transformed and/or supplementedrepresentation of a primary data object and/or metadata that isdifferent from the original format, e.g., in a compressed, encrypted,deduplicated, or other modified format. For instance, secondary storagecomputing devices 106 can generate new metadata or other informationbased on said processing, and store the newly generated informationalong with the secondary copies. Secondary copy data object 1346represents primary data objects 120, 1336, and 119A as 120′, 133B′, and119A′, respectively, accompanied by corresponding metadata Meta2,Meta10, and Meta1, respectively. Also, secondary copy data object 134Crepresents primary data objects 133A, 1196, and 129A as 133A′, 1196′,and 129A′, respectively, accompanied by corresponding metadata Meta9,Meta5, and Meta6, respectively.

Exemplary Information Management System Architecture

System 100 can incorporate a variety of different hardware and softwarecomponents, which can in turn be organized with respect to one anotherin many different configurations, depending on the embodiment. There arecritical design choices involved in specifying the functionalresponsibilities of the components and the role of each component insystem 100. Such design choices can impact how system 100 performs andadapts to data growth and other changing circumstances. FIG. 1C shows asystem 100 designed according to these considerations and includes:storage manager 140, one or more data agents 142 executing on clientcomputing device(s) 102 and configured to process primary data 112, andone or more media agents 144 executing on one or more secondary storagecomputing devices 106 for performing tasks involving secondary storagedevices 108.

Storage Manager

Storage manager 140 is a centralized storage and/or information managerthat is configured to perform certain control functions and also tostore certain critical information about system 100—hence storagemanager 140 is said to manage system 100. As noted, the number ofcomponents in system 100 and the amount of data under management can belarge. Managing the components and data is therefore a significant task,which can grow unpredictably as the number of components and data scaleto meet the needs of the organization. For these and other reasons,according to certain embodiments, responsibility for controlling system100, or at least a significant portion of that responsibility, isallocated to storage manager 140. Storage manager 140 can be adaptedindependently according to changing circumstances, without having toreplace or re-design the remainder of the system. Moreover, a computingdevice for hosting and/or operating as storage manager 140 can beselected to best suit the functions and networking needs of storagemanager 140. These and other advantages are described in further detailbelow and with respect to FIG. 1D.

Storage manager 140 may be a software module or other application hostedby a suitable computing device. In some embodiments, storage manager 140is itself a computing device that performs the functions describedherein. Storage manager 140 comprises or operates in conjunction withone or more associated data structures such as a dedicated database(e.g., management database 146), depending on the configuration. Thestorage manager 140 generally initiates, performs, coordinates, and/orcontrols storage and other information management operations performedby system 100, e.g., to protect and control primary data 112 andsecondary copies 116. In general, storage manager 140 is said to managesystem 100, which includes communicating with, instructing, andcontrolling in some circumstances components such as data agents 142 andmedia agents 144, etc.

As shown by the dashed arrowed lines 114 in FIG. 1C, storage manager 140may communicate with, instruct, and/or control some or all elements ofsystem 100, such as data agents 142 and media agents 144. In thismanner, storage manager 140 manages the operation of various hardwareand software components in system 100. In certain embodiments, controlinformation originates from storage manager 140 and status as well asindex reporting is transmitted to storage manager 140 by the managedcomponents, whereas payload data and metadata are generally communicatedbetween data agents 142 and media agents 144 (or otherwise betweenclient computing device(s) 102 and secondary storage computing device(s)106), e.g., at the direction of and under the management of storagemanager 140. Control information can generally include parameters andinstructions for carrying out information management operations, suchas, without limitation, instructions to perform a task associated withan operation, timing information specifying when to initiate a task,data path information specifying what components to communicate with oraccess in carrying out an operation, and the like. In other embodiments,some information management operations are controlled or initiated byother components of system 100 (e.g., by media agents 144 or data agents142), instead of or in combination with storage manager 140.

According to certain embodiments, storage manager 140 provides one ormore of the following functions:

-   -   communicating with data agents 142 and media agents 144,        including transmitting instructions, messages, and/or queries,        as well as receiving status reports, index information,        messages, and/or queries, and responding to same;    -   initiating execution of information management operations;    -   initiating restore and recovery operations;    -   managing secondary storage devices 108 and inventory/capacity of        the same;    -   allocating secondary storage devices 108 for secondary copy        operations;    -   reporting, searching, and/or classification of data in system        100;    -   monitoring completion of and status reporting related to        information management operations and jobs;    -   tracking movement of data within system 100;    -   tracking age information relating to secondary copies 116,        secondary storage devices 108, comparing the age information        against retention guidelines, and initiating data pruning when        appropriate;    -   tracking logical associations between components in system 100;    -   protecting metadata associated with system 100, e.g., in        management database 146;    -   implementing job management, schedule management, event        management, alert management, reporting, job history        maintenance, user security management, disaster recovery        management, and/or user interfacing for system administrators        and/or end users of system 100;    -   sending, searching, and/or viewing of log files; and    -   implementing operations management functionality.

Storage manager 140 may maintain an associated database 146 (or “storagemanager database 146” or “management database 146”) ofmanagement-related data and information management policies 148.Database 146 is stored in computer memory accessible by storage manager140. Database 146 may include a management index 150 (or “index 150”) orother data structure(s) that may store: logical associations betweencomponents of the system; user preferences and/or profiles (e.g.,preferences regarding encryption, compression, or deduplication ofprimary data or secondary copies; preferences regarding the scheduling,type, or other aspects of secondary copy or other operations; mappingsof particular information management users or user accounts to certaincomputing devices or other components, etc.; management tasks; mediacontainerization; other useful data; and/or any combination thereof. Forexample, storage manager 140 may use index 150 to track logicalassociations between media agents 144 and secondary storage devices 108and/or movement of data to/from secondary storage devices 108. Forinstance, index 150 may store data associating a client computing device102 with a particular media agent 144 and/or secondary storage device108, as specified in an information management policy 148.

Administrators and others may configure and initiate certain informationmanagement operations on an individual basis. But while this may beacceptable for some recovery operations or other infrequent tasks, it isoften not workable for implementing on-going organization-wide dataprotection and management. Thus, system 100 may utilize informationmanagement policies 148 for specifying and executing informationmanagement operations on an automated basis. Generally, an informationmanagement policy 148 can include a stored data structure or otherinformation source that specifies parameters (e.g., criteria and rules)associated with storage management or other information managementoperations. Storage manager 140 can process an information managementpolicy 148 and/or index 150 and, based on the results, identify aninformation management operation to perform, identify the appropriatecomponents in system 100 to be involved in the operation (e.g., clientcomputing devices 102 and corresponding data agents 142, secondarystorage computing devices 106 and corresponding media agents 144, etc.),establish connections to those components and/or between thosecomponents, and/or instruct and control those components to carry outthe operation. In this manner, system 100 can translate storedinformation into coordinated activity among the various computingdevices in system 100.

Management database 146 may maintain information management policies 148and associated data, although information management policies 148 can bestored in computer memory at any appropriate location outside managementdatabase 146. For instance, an information management policy 148 such asa storage policy may be stored as metadata in a media agent database 152or in a secondary storage device 108 (e.g., as an archive copy) for usein restore or other information management operations, depending on theembodiment. Information management policies 148 are described furtherbelow. According to certain embodiments, management database 146comprises a relational database (e.g., an SQL database) for trackingmetadata, such as metadata associated with secondary copy operations(e.g., what client computing devices 102 and corresponding subclientdata were protected and where the secondary copies are stored and whichmedia agent 144 performed the storage operation(s)). This and othermetadata may additionally be stored in other locations, such as atsecondary storage computing device 106 or on the secondary storagedevice 108, allowing data recovery without the use of storage manager140 in some cases. Thus, management database 146 may comprise dataneeded to kick off secondary copy operations (e.g., storage policies,schedule policies, etc.), status and reporting information aboutcompleted jobs (e.g., status and error reports on yesterday's backupjobs), and additional information sufficient to enable restore anddisaster recovery operations (e.g., media agent associations, locationindexing, content indexing, etc.).

Storage manager 140 may include a jobs agent 156, a user interface 158,and a management agent 154, all of which may be implemented asinterconnected software modules or application programs. These aredescribed further below.

Jobs agent 156 in some embodiments initiates, controls, and/or monitorsthe status of some or all information management operations previouslyperformed, currently being performed, or scheduled to be performed bysystem 100. A job is a logical grouping of information managementoperations such as daily storage operations scheduled for a certain setof subclients (e.g., generating incremental block-level backup copies116 at a certain time every day for database files in a certaingeographical location). Thus, jobs agent 156 may access informationmanagement policies 148 (e.g., in management database 146) to determinewhen, where, and how to initiate/control jobs in system 100.

Storage Manager User Interfaces

User interface 158 may include information processing and displaysoftware, such as a graphical user interface (GUI), an applicationprogram interface (API), and/or other interactive interface(s) throughwhich users and system processes can retrieve information about thestatus of information management operations or issue instructions tostorage manager 140 and other components. Via user interface 158, usersmay issue instructions to the components in system 100 regardingperformance of secondary copy and recovery operations. For example, auser may modify a schedule concerning the number of pending secondarycopy operations. As another example, a user may employ the GUI to viewthe status of pending secondary copy jobs or to monitor the status ofcertain components in system 100 (e.g., the amount of capacity left in astorage device). Storage manager 140 may track information that permitsit to select, designate, or otherwise identify content indices,deduplication databases, or similar databases or resources or data setswithin its information management cell (or another cell) to be searchedin response to certain queries. Such queries may be entered by the userby interacting with user interface 158.

Various embodiments of information management system 100 may beconfigured and/or designed to generate user interface data usable forrendering the various interactive user interfaces described. The userinterface data may be used by system 100 and/or by another system,device, and/or software program (for example, a browser program), torender the interactive user interfaces. The interactive user interfacesmay be displayed on, for example, electronic displays (including, forexample, touch-enabled displays), consoles, etc., whetherdirect-connected to storage manager 140 or communicatively coupledremotely, e.g., via an internet connection. The present disclosuredescribes various embodiments of interactive and dynamic userinterfaces, some of which may be generated by user interface agent 158,and which are the result of significant technological development. Theuser interfaces described herein may provide improved human-computerinteractions, allowing for significant cognitive and ergonomicefficiencies and advantages over previous systems, including reducedmental workloads, improved decision-making, and the like. User interface158 may operate in a single integrated view or console (not shown). Theconsole may support a reporting capability for generating a variety ofreports, which may be tailored to a particular aspect of informationmanagement.

User interfaces are not exclusive to storage manager 140 and in someembodiments a user may access information locally from a computingdevice component of system 100. For example, some information pertainingto installed data agents 142 and associated data streams may beavailable from client computing device 102. Likewise, some informationpertaining to media agents 144 and associated data streams may beavailable from secondary storage computing device 106.

Storage Manager Management Agent

Management agent 154 can provide storage manager 140 with the ability tocommunicate with other components within system 100 and/or with otherinformation management cells via network protocols and applicationprogramming interfaces (APIs) including, e.g., HTTP, HTTPS, FTP, REST,virtualization software APIs, cloud service provider APIs, and hostedservice provider APIs, without limitation. Management agent 154 alsoallows multiple information management cells to communicate with oneanother. For example, system 100 in some cases may be one informationmanagement cell in a network of multiple cells adjacent to one anotheror otherwise logically related, e.g., in a WAN or LAN. With thisarrangement, the cells may communicate with one another throughrespective management agents 154. Inter-cell communications andhierarchy is described in greater detail in e.g., U.S. Pat. No.7,343,453.

Information Management Cell

An “information management cell” (or “storage operation cell” or “cell”)may generally include a logical and/or physical grouping of acombination of hardware and software components associated withperforming information management operations on electronic data,typically one storage manager 140 and at least one data agent 142(executing on a client computing device 102) and at least one mediaagent 144 (executing on a secondary storage computing device 106). Forinstance, the components shown in FIG. 1C may together form aninformation management cell. Thus, in some configurations, a system 100may be referred to as an information management cell or a storageoperation cell. A given cell may be identified by the identity of itsstorage manager 140, which is generally responsible for managing thecell.

Multiple cells may be organized hierarchically, so that cells mayinherit properties from hierarchically superior cells or be controlledby other cells in the hierarchy (automatically or otherwise).Alternatively, in some embodiments, cells may inherit or otherwise beassociated with information management policies, preferences,information management operational parameters, or other properties orcharacteristics according to their relative position in a hierarchy ofcells. Cells may also be organized hierarchically according to function,geography, architectural considerations, or other factors useful ordesirable in performing information management operations. For example,a first cell may represent a geographic segment of an enterprise, suchas a Chicago office, and a second cell may represent a differentgeographic segment, such as a New York City office. Other cells mayrepresent departments within a particular office, e.g., human resources,finance, engineering, etc. Where delineated by function, a first cellmay perform one or more first types of information management operations(e.g., one or more first types of secondary copies at a certainfrequency), and a second cell may perform one or more second types ofinformation management operations (e.g., one or more second types ofsecondary copies at a different frequency and under different retentionrules). In general, the hierarchical information is maintained by one ormore storage managers 140 that manage the respective cells (e.g., incorresponding management database(s) 146).

Data Agents

A variety of different applications 110 can operate on a given clientcomputing device 102, including operating systems, file systems,database applications, e-mail applications, and virtual machines, justto name a few. And, as part of the process of creating and restoringsecondary copies 116, the client computing device 102 may be tasked withprocessing and preparing the primary data 112 generated by these variousapplications 110. Moreover, the nature of the processing/preparation candiffer across application types, e.g., due to inherent structural,state, and formatting differences among applications 110 and/or theoperating system of client computing device 102. Each data agent 142 istherefore advantageously configured in some embodiments to assist in theperformance of information management operations based on the type ofdata that is being protected at a client-specific and/orapplication-specific level.

Data agent 142 is a component of information system 100 and is generallydirected by storage manager 140 to participate in creating or restoringsecondary copies 116. Data agent 142 may be a software program (e.g., inthe form of a set of executable binary files) that executes on the sameclient computing device 102 as the associated application 110 that dataagent 142 is configured to protect. Data agent 142 is generallyresponsible for managing, initiating, or otherwise assisting in theperformance of information management operations in reference to itsassociated application(s) 110 and corresponding primary data 112 whichis generated/accessed by the particular application(s) 110. Forinstance, data agent 142 may take part in copying, archiving, migrating,and/or replicating of certain primary data 112 stored in the primarystorage device(s) 104. Data agent 142 may receive control informationfrom storage manager 140, such as commands to transfer copies of dataobjects and/or metadata to one or more media agents 144. Data agent 142also may compress, deduplicate, and encrypt certain primary data 112, aswell as capture application-related metadata before transmitting theprocessed data to media agent 144. Data agent 142 also may receiveinstructions from storage manager 140 to restore (or assist inrestoring) a secondary copy 116 from secondary storage device 108 toprimary storage 104, such that the restored data may be properlyaccessed by application 110 in a suitable format as though it wereprimary data 112.

Each data agent 142 may be specialized for a particular application 110.For instance, different individual data agents 142 may be designed tohandle Microsoft Exchange data, Lotus Notes data, Microsoft Windows filesystem data, Microsoft Active Directory Objects data, SQL Server data,Share Point data, Oracle database data, SAP database data, virtualmachines and/or associated data, and other types of data. A file systemdata agent, for example, may handle data files and/or other file systeminformation. If a client computing device 102 has two or more types ofdata 112, a specialized data agent 142 may be used for each data type.For example, to backup, migrate, and/or restore all of the data on aMicrosoft Exchange server, the client computing device 102 may use: (1)a Microsoft Exchange Mailbox data agent 142 to back up the Exchangemailboxes; (2) a Microsoft Exchange Database data agent 142 to back upthe Exchange databases; (3) a Microsoft Exchange Public Folder dataagent 142 to back up the Exchange Public Folders; and (4) a MicrosoftWindows File System data agent 142 to back up the file system of clientcomputing device 102. In this example, these specialized data agents 142are treated as four separate data agents 142 even though they operate onthe same client computing device 102. Other examples may include archivemanagement data agents such as a migration archiver or a compliancearchiver, Quick Recovery® agents, and continuous data replicationagents. Application-specific data agents 142 can provide improvedperformance as compared to generic agents. For instance, becauseapplication-specific data agents 142 may only handle data for a singlesoftware application, the design, operation, and performance of the dataagent 142 can be streamlined. The data agent 142 may therefore executefaster and consume less persistent storage and/or operating memory thandata agents designed to generically accommodate multiple differentsoftware applications 110.

Each data agent 142 may be configured to access data and/or metadatastored in the primary storage device(s) 104 associated with data agent142 and its host client computing device 102, and process the dataappropriately. For example, during a secondary copy operation, dataagent 142 may arrange or assemble the data and metadata into one or morefiles having a certain format (e.g., a particular backup or archiveformat) before transferring the file(s) to a media agent 144 or othercomponent. The file(s) may include a list of files or other metadata. Insome embodiments, a data agent 142 may be distributed between clientcomputing device 102 and storage manager 140 (and any other intermediatecomponents) or may be deployed from a remote location or its functionsapproximated by a remote process that performs some or all of thefunctions of data agent 142. In addition, a data agent 142 may performsome functions provided by media agent 144. Other embodiments may employone or more generic data agents 142 that can handle and process datafrom two or more different applications 110, or that can handle andprocess multiple data types, instead of or in addition to usingspecialized data agents 142. For example, one generic data agent 142 maybe used to back up, migrate and restore Microsoft Exchange Mailbox dataand Microsoft Exchange Database data, while another generic data agentmay handle Microsoft Exchange Public Folder data and Microsoft WindowsFile System data.

Media Agents

As noted, off-loading certain responsibilities from client computingdevices 102 to intermediate components such as secondary storagecomputing device(s) 106 and corresponding media agent(s) 144 can providea number of benefits including improved performance of client computingdevice 102, faster and more reliable information management operations,and enhanced scalability. In one example which will be discussed furtherbelow, media agent 144 can act as a local cache of recently-copied dataand/or metadata stored to secondary storage device(s) 108, thusimproving restore capabilities and performance for the cached data.

Media agent 144 is a component of system 100 and is generally directedby storage manager 140 in creating and restoring secondary copies 116.Whereas storage manager 140 generally manages system 100 as a whole,media agent 144 provides a portal to certain secondary storage devices108, such as by having specialized features for communicating with andaccessing certain associated secondary storage device 108. Media agent144 may be a software program (e.g., in the form of a set of executablebinary files) that executes on a secondary storage computing device 106.Media agent 144 generally manages, coordinates, and facilitates thetransmission of data between a data agent 142 (executing on clientcomputing device 102) and secondary storage device(s) 108 associatedwith media agent 144. For instance, other components in the system mayinteract with media agent 144 to gain access to data stored onassociated secondary storage device(s) 108, (e.g., to browse, read,write, modify, delete, or restore data). Moreover, media agents 144 cangenerate and store information relating to characteristics of the storeddata and/or metadata, or can generate and store other types ofinformation that generally provides insight into the contents of thesecondary storage devices 108—generally referred to as indexing of thestored secondary copies 116. Each media agent 144 may operate on adedicated secondary storage computing device 106, while in otherembodiments a plurality of media agents 144 may operate on the samesecondary storage computing device 106.

A media agent 144 may be associated with a particular secondary storagedevice 108 if that media agent 144 is capable of one or more of: routingand/or storing data to the particular secondary storage device 108;coordinating the routing and/or storing of data to the particularsecondary storage device 108; retrieving data from the particularsecondary storage device 108; coordinating the retrieval of data fromthe particular secondary storage device 108; and modifying and/ordeleting data retrieved from the particular secondary storage device108. Media agent 144 in certain embodiments is physically separate fromthe associated secondary storage device 108. For instance, a media agent144 may operate on a secondary storage computing device 106 in adistinct housing, package, and/or location from the associated secondarystorage device 108. In one example, a media agent 144 operates on afirst server computer and is in communication with a secondary storagedevice(s) 108 operating in a separate rack-mounted RAID-based system.

A media agent 144 associated with a particular secondary storage device108 may instruct secondary storage device 108 to perform an informationmanagement task. For instance, a media agent 144 may instruct a tapelibrary to use a robotic arm or other retrieval means to load or eject acertain storage media, and to subsequently archive, migrate, or retrievedata to or from that media, e.g., for the purpose of restoring data to aclient computing device 102. As another example, a secondary storagedevice 108 may include an array of hard disk drives or solid statedrives organized in a RAID configuration, and media agent 144 mayforward a logical unit number (LUN) and other appropriate information tothe array, which uses the received information to execute the desiredsecondary copy operation. Media agent 144 may communicate with asecondary storage device 108 via a suitable communications link, such asa SCSI or Fibre Channel link.

Each media agent 144 may maintain an associated media agent database152. Media agent database 152 may be stored to a disk or other storagedevice (not shown) that is local to the secondary storage computingdevice 106 on which media agent 144 executes. In other cases, mediaagent database 152 is stored separately from the host secondary storagecomputing device 106. Media agent database 152 can include, among otherthings, a media agent index 153 (see, e.g., FIG. 1C). In some cases,media agent index 153 does not form a part of and is instead separatefrom media agent database 152.

Media agent index 153 (or “index 153”) may be a data structureassociated with the particular media agent 144 that includes informationabout the stored data associated with the particular media agent andwhich may be generated in the course of performing a secondary copyoperation or a restore. Index 153 provides a fast and efficientmechanism for locating/browsing secondary copies 116 or other datastored in secondary storage devices 108 without having to accesssecondary storage device 108 to retrieve the information from there. Forinstance, for each secondary copy 116, index 153 may include metadatasuch as a list of the data objects (e.g., files/subdirectories, databaseobjects, mailbox objects, etc.), a logical path to the secondary copy116 on the corresponding secondary storage device 108, locationinformation (e.g., offsets) indicating where the data objects are storedin the secondary storage device 108, when the data objects were createdor modified, etc. Thus, index 153 includes metadata associated with thesecondary copies 116 that is readily available for use from media agent144. In some embodiments, some or all of the information in index 153may instead or additionally be stored along with secondary copies 116 insecondary storage device 108. In some embodiments, a secondary storagedevice 108 can include sufficient information to enable a “bare metalrestore,” where the operating system and/or software applications of afailed client computing device 102 or another target may beautomatically restored without manually reinstalling individual softwarepackages (including operating systems).

Because index 153 may operate as a cache, it can also be referred to asan “index cache.” In such cases, information stored in index cache 153typically comprises data that reflects certain particulars aboutrelatively recent secondary copy operations. After some triggeringevent, such as after some time elapses or index cache 153 reaches aparticular size, certain portions of index cache 153 may be copied ormigrated to secondary storage device 108, e.g., on a least-recently-usedbasis. This information may be retrieved and uploaded back into indexcache 153 or otherwise restored to media agent 144 to facilitateretrieval of data from the secondary storage device(s) 108. In someembodiments, the cached information may include format orcontainerization information related to archives or other files storedon storage device(s) 108.

In some alternative embodiments media agent 144 generally acts as acoordinator or facilitator of secondary copy operations between clientcomputing devices 102 and secondary storage devices 108, but does notactually write the data to secondary storage device 108. For instance,storage manager 140 (or media agent 144) may instruct a client computingdevice 102 and secondary storage device 108 to communicate with oneanother directly. In such a case, client computing device 102 transmitsdata directly or via one or more intermediary components to secondarystorage device 108 according to the received instructions, and viceversa. Media agent 144 may still receive, process, and/or maintainmetadata related to the secondary copy operations, i.e., may continue tobuild and maintain index 153. In these embodiments, payload data canflow through media agent 144 for the purposes of populating index 153,but not for writing to secondary storage device 108. Media agent 144and/or other components such as storage manager 140 may in some casesincorporate additional functionality, such as data classification,content indexing, deduplication, encryption, compression, and the like.Further details regarding these and other functions are described below.

Distributed, Scalable Architecture

As described, certain functions of system 100 can be distributed amongstvarious physical and/or logical components. For instance, one or more ofstorage manager 140, data agents 142, and media agents 144 may operateon computing devices that are physically separate from one another. Thisarchitecture can provide a number of benefits. For instance, hardwareand software design choices for each distributed component can betargeted to suit its particular function. The secondary computingdevices 106 on which media agents 144 operate can be tailored forinteraction with associated secondary storage devices 108 and providefast index cache operation, among other specific tasks. Similarly,client computing device(s) 102 can be selected to effectively serviceapplications 110 in order to efficiently produce and store primary data112.

Moreover, in some cases, one or more of the individual components ofinformation management system 100 can be distributed to multipleseparate computing devices. As one example, for large file systems wherethe amount of data stored in management database 146 is relativelylarge, database 146 may be migrated to or may otherwise reside on aspecialized database server (e.g., an SQL server) separate from a serverthat implements the other functions of storage manager 140. Thisdistributed configuration can provide added protection because database146 can be protected with standard database utilities (e.g., SQL logshipping or database replication) independent from other functions ofstorage manager 140. Database 146 can be efficiently replicated to aremote site for use in the event of a disaster or other data loss at theprimary site. Or database 146 can be replicated to another computingdevice within the same site, such as to a higher performance machine inthe event that a storage manager host computing device can no longerservice the needs of a growing system 100.

The distributed architecture also provides scalability and efficientcomponent utilization. FIG. 1D shows an embodiment of informationmanagement system 100 including a plurality of client computing devices102 and associated data agents 142 as well as a plurality of secondarystorage computing devices 106 and associated media agents 144.Additional components can be added or subtracted based on the evolvingneeds of system 100. For instance, depending on where bottlenecks areidentified, administrators can add additional client computing devices102, secondary storage computing devices 106, and/or secondary storagedevices 108. Moreover, where multiple fungible components are available,load balancing can be implemented to dynamically address identifiedbottlenecks. As an example, storage manager 140 may dynamically selectwhich media agents 144 and/or secondary storage devices 108 to use forstorage operations based on a processing load analysis of media agents144 and/or secondary storage devices 108, respectively.

Where system 100 includes multiple media agents 144 (see, e.g., FIG.1D), a first media agent 144 may provide failover functionality for asecond failed media agent 144. In addition, media agents 144 can bedynamically selected to provide load balancing. Each client computingdevice 102 can communicate with, among other components, any of themedia agents 144, e.g., as directed by storage manager 140. And eachmedia agent 144 may communicate with, among other components, any ofsecondary storage devices 108, e.g., as directed by storage manager 140.Thus, operations can be routed to secondary storage devices 108 in adynamic and highly flexible manner, to provide load balancing, failover,etc. Further examples of scalable systems capable of dynamic storageoperations, load balancing, and failover are provided in U.S. Pat. No.7,246,207.

While distributing functionality amongst multiple computing devices canhave certain advantages, in other contexts it can be beneficial toconsolidate functionality on the same computing device. In alternativeconfigurations, certain components may reside and execute on the samecomputing device. As such, in other embodiments, one or more of thecomponents shown in FIG. 1C may be implemented on the same computingdevice. In one configuration, a storage manager 140, one or more dataagents 142, and/or one or more media agents 144 are all implemented onthe same computing device. In other embodiments, one or more data agents142 and one or more media agents 144 are implemented on the samecomputing device, while storage manager 140 is implemented on a separatecomputing device, etc. without limitation.

Exemplary Types of Information Management Operations, Including StorageOperations

In order to protect and leverage stored data, system 100 can beconfigured to perform a variety of information management operations,which may also be referred to in some cases as storage managementoperations or storage operations. These operations can generally include(i) data movement operations, (ii) processing and data manipulationoperations, and (iii) analysis, reporting, and management operations.

Data Movement Operations, Including Secondary Copy Operations

Data movement operations are generally storage operations that involvethe copying or migration of data between different locations in system100. For example, data movement operations can include operations inwhich stored data is copied, migrated, or otherwise transferred from oneor more first storage devices to one or more second storage devices,such as from primary storage device(s) 104 to secondary storagedevice(s) 108, from secondary storage device(s) 108 to differentsecondary storage device(s) 108, from secondary storage devices 108 toprimary storage devices 104, or from primary storage device(s) 104 todifferent primary storage device(s) 104, or in some cases within thesame primary storage device 104 such as within a storage array.

Data movement operations can include by way of example, backupoperations, archive operations, information lifecycle managementoperations such as hierarchical storage management operations,replication operations (e.g., continuous data replication), snapshotoperations, deduplication or single-instancing operations, auxiliarycopy operations, disaster-recovery copy operations, and the like. Aswill be discussed, some of these operations do not necessarily createdistinct copies. Nonetheless, some or all of these operations aregenerally referred to as “secondary copy operations” for simplicity,because they involve secondary copies. Data movement also comprisesrestoring secondary copies.

Backup Operations

A backup operation creates a copy of a version of primary data 112 at aparticular point in time (e.g., one or more files or other data units).Each subsequent backup copy 116 (which is a form of secondary copy 116)may be maintained independently of the first. A backup generallyinvolves maintaining a version of the copied primary data 112 as well asbackup copies 116. Further, a backup copy in some embodiments isgenerally stored in a form that is different from the native format,e.g., a backup format. This contrasts to the version in primary data 112which may instead be stored in a format native to the sourceapplication(s) 110. In various cases, backup copies can be stored in aformat in which the data is compressed, encrypted, deduplicated, and/orotherwise modified from the original native application format. Forexample, a backup copy may be stored in a compressed backup format thatfacilitates efficient long-term storage. Backup copies 116 can haverelatively long retention periods as compared to primary data 112, whichis generally highly changeable. Backup copies 116 may be stored on mediawith slower retrieval times than primary storage device 104. Some backupcopies may have shorter retention periods than some other types ofsecondary copies 116, such as archive copies (described below). Backupsmay be stored at an offsite location.

Backup operations can include full backups, differential backups,incremental backups, “synthetic full” backups, and/or creating a“reference copy.” A full backup (or “standard full backup”) in someembodiments is generally a complete image of the data to be protected.However, because full backup copies can consume a relatively largeamount of storage, it can be useful to use a full backup copy as abaseline and only store changes relative to the full backup copyafterwards.

A differential backup operation (or cumulative incremental backupoperation) tracks and stores changes that occurred since the last fullbackup. Differential backups can grow quickly in size, but can restorerelatively efficiently because a restore can be completed in some casesusing only the full backup copy and the latest differential copy.

An incremental backup operation generally tracks and stores changessince the most recent backup copy of any type, which can greatly reducestorage utilization. In some cases, however, restoring can be lengthycompared to full or differential backups because completing a restoreoperation may involve accessing a full backup in addition to multipleincremental backups.

Synthetic full backups generally consolidate data without directlybacking up data from the client computing device. A synthetic fullbackup is created from the most recent full backup (i.e., standard orsynthetic) and subsequent incremental and/or differential backups. Theresulting synthetic full backup is identical to what would have beencreated had the last backup for the subclient been a standard fullbackup. Unlike standard full, incremental, and differential backups,however, a synthetic full backup does not actually transfer data fromprimary storage to the backup media, because it operates as a backupconsolidator. A synthetic full backup extracts the index data of eachparticipating subclient. Using this index data and the previously backedup user data images, it builds new full backup images (e.g., bitmaps),one for each subclient. The new backup images consolidate the index anduser data stored in the related incremental, differential, and previousfull backups into a synthetic backup file that fully represents thesubclient (e.g., via pointers) but does not comprise all its constituentdata.

Any of the above types of backup operations can be at the volume level,file level, or block level. Volume level backup operations generallyinvolve copying of a data volume (e.g., a logical disk or partition) asa whole. In a file-level backup, information management system 100generally tracks changes to individual files and includes copies offiles in the backup copy. For block-level backups, files are broken intoconstituent blocks, and changes are tracked at the block level. Uponrestore, system 100 reassembles the blocks into files in a transparentfashion. Far less data may actually be transferred and copied tosecondary storage devices 108 during a file-level copy than avolume-level copy. Likewise, a block-level copy may transfer less datathan a file-level copy, resulting in faster execution. However,restoring a relatively higher-granularity copy can result in longerrestore times. For instance, when restoring a block-level copy, theprocess of locating and retrieving constituent blocks can sometimes takelonger than restoring file-level backups.

A reference copy may comprise copy(ies) of selected objects from backedup data, typically to help organize data by keeping contextualinformation from multiple sources together, and/or help retain specificdata for a longer period of time, such as for legal hold needs. Areference copy generally maintains data integrity, and when the data isrestored, it may be viewed in the same format as the source data. Insome embodiments, a reference copy is based on a specialized client,individual subclient and associated information management policies(e.g., storage policy, retention policy, etc.) that are administeredwithin system 100.

Archive Operations

Because backup operations generally involve maintaining a version of thecopied primary data 112 and also maintaining backup copies in secondarystorage device(s) 108, they can consume significant storage capacity. Toreduce storage consumption, an archive operation according to certainembodiments creates an archive copy 116 by both copying and removingsource data. Or, seen another way, archive operations can involve movingsome or all of the source data to the archive destination. Thus, datasatisfying criteria for removal (e.g., data of a threshold age or size)may be removed from source storage. The source data may be primary data112 or a secondary copy 116, depending on the situation. As with backupcopies, archive copies can be stored in a format in which the data iscompressed, encrypted, deduplicated, and/or otherwise modified from theformat of the original application or source copy. In addition, archivecopies may be retained for relatively long periods of time (e.g., years)and, in some cases are never deleted. In certain embodiments, archivecopies may be made and kept for extended periods in order to meetcompliance regulations.

Archiving can also serve the purpose of freeing up space in primarystorage device(s) 104 and easing the demand on computational resourceson client computing device 102. Similarly, when a secondary copy 116 isarchived, the archive copy can therefore serve the purpose of freeing upspace in the source secondary storage device(s) 108. Examples of dataarchiving operations are provided in U.S. Pat. No. 7,107,298.

Snapshot Operations

Snapshot operations can provide a relatively lightweight, efficientmechanism for protecting data. From an end-user viewpoint, a snapshotmay be thought of as an “instant” image of primary data 112 at a givenpoint in time, and may include state and/or status information relativeto an application 110 that creates/manages primary data 112. In oneembodiment, a snapshot may generally capture the directory structure ofan object in primary data 112 such as a file or volume or other data setat a particular moment in time and may also preserve file attributes andcontents. A snapshot in some cases is created relatively quickly, e.g.,substantially instantly, using a minimum amount of file space, but maystill function as a conventional file system backup.

A “hardware snapshot” (or “hardware-based snapshot”) operation occurswhere a target storage device (e.g., a primary storage device 104 or asecondary storage device 108) performs the snapshot operation in aself-contained fashion, substantially independently, using hardware,firmware and/or software operating on the storage device itself. Forinstance, the storage device may perform snapshot operations generallywithout intervention or oversight from any of the other components ofthe system 100, e.g., a storage array may generate an “array-created”hardware snapshot and may also manage its storage, integrity,versioning, etc. In this manner, hardware snapshots can off-load othercomponents of system 100 from snapshot processing. An array may receivea request from another component to take a snapshot and then proceed toexecute the “hardware snapshot” operations autonomously, preferablyreporting success to the requesting component.

A “software snapshot” (or “software-based snapshot”) operation, on theother hand, occurs where a component in system 100 (e.g., clientcomputing device 102, etc.) implements a software layer that manages thesnapshot operation via interaction with the target storage device. Forinstance, the component executing the snapshot management software layermay derive a set of pointers and/or data that represents the snapshot.The snapshot management software layer may then transmit the same to thetarget storage device, along with appropriate instructions for writingthe snapshot. One example of a software snapshot product is MicrosoftVolume Snapshot Service (VSS), which is part of the Microsoft Windowsoperating system.

Some types of snapshots do not actually create another physical copy ofall the data as it existed at the particular point in time, but maysimply create pointers that map files and directories to specific memorylocations (e.g., to specific disk blocks) where the data resides as itexisted at the particular point in time. For example, a snapshot copymay include a set of pointers derived from the file system or from anapplication. In some other cases, the snapshot may be created at theblock-level, such that creation of the snapshot occurs without awarenessof the file system. Each pointer points to a respective stored datablock, so that collectively, the set of pointers reflect the storagelocation and state of the data object (e.g., file(s) or volume(s) ordata set(s)) at the point in time when the snapshot copy was created.

An initial snapshot may use only a small amount of disk space needed torecord a mapping or other data structure representing or otherwisetracking the blocks that correspond to the current state of the filesystem. Additional disk space is usually required only when files anddirectories change later on. Furthermore, when files change, typicallyonly the pointers which map to blocks are copied, not the blocksthemselves. For example for “copy-on-write” snapshots, when a blockchanges in primary storage, the block is copied to secondary storage orcached in primary storage before the block is overwritten in primarystorage, and the pointer to that block is changed to reflect the newlocation of that block. The snapshot mapping of file system data mayalso be updated to reflect the changed block(s) at that particular pointin time. In some other cases, a snapshot includes a full physical copyof all or substantially all of the data represented by the snapshot.Further examples of snapshot operations are provided in U.S. Pat. No.7,529,782. A snapshot copy in many cases can be made quickly and withoutsignificantly impacting primary computing resources because largeamounts of data need not be copied or moved. In some embodiments, asnapshot may exist as a virtual file system, parallel to the actual filesystem. Users in some cases gain read-only access to the record of filesand directories of the snapshot. By electing to restore primary data 112from a snapshot taken at a given point in time, users may also returnthe current file system to the state of the file system that existedwhen the snapshot was taken.

Replication Operations

Replication is another type of secondary copy operation. Some types ofsecondary copies 116 periodically capture images of primary data 112 atparticular points in time (e.g., backups, archives, and snapshots).However, it can also be useful for recovery purposes to protect primarydata 112 in a more continuous fashion, by replicating primary data 112substantially as changes occur. In some cases a replication copy can bea mirror copy, for instance, where changes made to primary data 112 aremirrored or substantially immediately copied to another location (e.g.,to secondary storage device(s) 108). By copying each write operation tothe replication copy, two storage systems are kept synchronized orsubstantially synchronized so that they are virtually identical atapproximately the same time. Where entire disk volumes are mirrored,however, mirroring can require significant amount of storage space andutilizes a large amount of processing resources.

According to some embodiments, secondary copy operations are performedon replicated data that represents a recoverable state, or “known goodstate” of a particular application running on the source system. Forinstance, in certain embodiments, known good replication copies may beviewed as copies of primary data 112. This feature allows the system todirectly access, copy, restore, back up, or otherwise manipulate thereplication copies as if they were the “live” primary data 112. This canreduce access time, storage utilization, and impact on sourceapplications 110, among other benefits. Based on known good stateinformation, system 100 can replicate sections of application data thatrepresent a recoverable state rather than rote copying of blocks ofdata. Examples of replication operations (e.g., continuous datareplication) are provided in U.S. Pat. No. 7,617,262.

Deduplication/Single-Instancing Operations

Deduplication or single-instance storage is useful to reduce the amountof non-primary data. For instance, some or all of the above-describedsecondary copy operations can involve deduplication in some fashion. Newdata is read, broken down into data portions of a selected granularity(e.g., sub-file level blocks, files, etc.), compared with correspondingportions that are already in secondary storage, and only new/changedportions are stored. Portions that already exist are represented aspointers to the already-stored data. Thus, a deduplicated secondary copy116 may comprise actual data portions copied from primary data 112 andmay further comprise pointers to already-stored data, which is generallymore storage-efficient than a full copy.

In order to streamline the comparison process, system 100 may calculateand/or store signatures (e.g., hashes or cryptographically unique IDs)corresponding to the individual source data portions and compare thesignatures to already-stored data signatures, instead of comparingentire data portions. In some cases, only a single instance of each dataportion is stored, and deduplication operations may therefore bereferred to interchangeably as “single-instancing” operations. Dependingon the implementation, however, deduplication operations can store morethan one instance of certain data portions, yet still significantlyreduce stored-data redundancy. Depending on the embodiment,deduplication portions such as data blocks can be of fixed or variablelength. Using variable length blocks can enhance deduplication byresponding to changes in the data stream, but can involve more complexprocessing. In some cases, system 100 utilizes a technique fordynamically aligning deduplication blocks based on changing content inthe data stream, as described in U.S. Pat. No. 8,364,652.

System 100 can deduplicate in a variety of manners at a variety oflocations. For instance, in some embodiments, system 100 implements“target-side” deduplication by deduplicating data at the media agent 144after being received from data agent 142. In some such cases, mediaagents 144 are generally configured to manage the deduplication process.For instance, one or more of the media agents 144 maintain acorresponding deduplication database that stores deduplicationinformation (e.g., data block signatures). Examples of such aconfiguration are provided in U.S. Pat. No. 9,020,900. Instead of or incombination with “target-side” deduplication, “source-side” (or“client-side”) deduplication can also be performed, e.g., to reduce theamount of data to be transmitted by data agent 142 to media agent 144.Storage manager 140 may communicate with other components within system100 via network protocols and cloud service provider APIs to facilitatecloud-based deduplication/single instancing, as exemplified in U.S. Pat.No. 8,954,446. Some other deduplication/single instancing techniques aredescribed in U.S. Pat. Pub. No. 2006/0224846 and in U.S. Pat. No.9,098,495.

Information Lifecycle Management and Hierarchical Storage Management

In some embodiments, files and other data over their lifetime move frommore expensive quick-access storage to less expensive slower-accessstorage. Operations associated with moving data through various tiers ofstorage are sometimes referred to as information lifecycle management(ILM) operations.

One type of ILM operation is a hierarchical storage management (HSM)operation, which generally automatically moves data between classes ofstorage devices, such as from high-cost to low-cost storage devices. Forinstance, an HSM operation may involve movement of data from primarystorage devices 104 to secondary storage devices 108, or between tiersof secondary storage devices 108. With each tier, the storage devicesmay be progressively cheaper, have relatively slower access/restoretimes, etc. For example, movement of data between tiers may occur asdata becomes less important over time. In some embodiments, an HSMoperation is similar to archiving in that creating an HSM copy may(though not always) involve deleting some of the source data, e.g.,according to one or more criteria related to the source data. Forexample, an HSM copy may include primary data 112 or a secondary copy116 that exceeds a given size threshold or a given age threshold. Often,and unlike some types of archive copies, HSM data that is removed oraged from the source is replaced by a logical reference pointer or stub.The reference pointer or stub can be stored in the primary storagedevice 104 or other source storage device, such as a secondary storagedevice 108 to replace the deleted source data and to point to orotherwise indicate the new location in (another) secondary storagedevice 108.

For example, files are generally moved between higher and lower coststorage depending on how often the files are accessed. When a userrequests access to HSM data that has been removed or migrated, system100 uses the stub to locate the data and can make recovery of the dataappear transparent, even though the HSM data may be stored at a locationdifferent from other source data. In this manner, the data appears tothe user (e.g., in file system browsing windows and the like) as if itstill resides in the source location (e.g., in a primary storage device104). The stub may include metadata associated with the correspondingdata, so that a file system and/or application can provide someinformation about the data object and/or a limited-functionality version(e.g., a preview) of the data object.

An HSM copy may be stored in a format other than the native applicationformat (e.g., compressed, encrypted, deduplicated, and/or otherwisemodified). In some cases, copies which involve the removal of data fromsource storage and the maintenance of stub or other logical referenceinformation on source storage may be referred to generally as “onlinearchive copies.” On the other hand, copies which involve the removal ofdata from source storage without the maintenance of stub or otherlogical reference information on source storage may be referred to as“off-line archive copies.” Examples of HSM and ILM techniques areprovided in U.S. Pat. No. 7,343,453.

Auxiliary Copy Operations

An auxiliary copy is generally a copy of an existing secondary copy 116.For instance, an initial secondary copy 116 may be derived from primarydata 112 or from data residing in secondary storage subsystem 118,whereas an auxiliary copy is generated from the initial secondary copy116. Auxiliary copies provide additional standby copies of data and mayreside on different secondary storage devices 108 than the initialsecondary copies 116. Thus, auxiliary copies can be used for recoverypurposes if initial secondary copies 116 become unavailable. Exemplaryauxiliary copy techniques are described in further detail in U.S. Pat.No. 8,230,195.

Disaster-Recovery Copy Operations

System 100 may also make and retain disaster recovery copies, often assecondary, high-availability disk copies. System 100 may createsecondary copies and store them at disaster recovery locations usingauxiliary copy or replication operations, such as continuous datareplication technologies. Depending on the particular data protectiongoals, disaster recovery locations can be remote from the clientcomputing devices 102 and primary storage devices 104, remote from someor all of the secondary storage devices 108, or both.

Data Manipulation, Including Encryption and Compression

Data manipulation and processing may include encryption and compressionas well as integrity marking and checking, formatting for transmission,formatting for storage, etc. Data may be manipulated “client-side” bydata agent 142 as well as “target-side” by media agent 144 in the courseof creating secondary copy 116, or conversely in the course of restoringdata from secondary to primary.

Encryption Operations

System 100 in some cases is configured to process data (e.g., files orother data objects, primary data 112, secondary copies 116, etc.),according to an appropriate encryption algorithm (e.g., Blowfish,Advanced Encryption Standard (AES), Triple Data Encryption Standard(3-DES), etc.) to limit access and provide data security. System 100 insome cases encrypts the data at the client level, such that clientcomputing devices 102 (e.g., data agents 142) encrypt the data prior totransferring it to other components, e.g., before sending the data tomedia agents 144 during a secondary copy operation. In such cases,client computing device 102 may maintain or have access to an encryptionkey or passphrase for decrypting the data upon restore. Encryption canalso occur when media agent 144 creates auxiliary copies or archivecopies. Encryption may be applied in creating a secondary copy 116 of apreviously unencrypted secondary copy 116, without limitation. Infurther embodiments, secondary storage devices 108 can implementbuilt-in, high performance hardware-based encryption.

Compression Operations

Similar to encryption, system 100 may also or alternatively compressdata in the course of generating a secondary copy 116. Compressionencodes information such that fewer bits are needed to represent theinformation as compared to the original representation. Compressiontechniques are well known in the art. Compression operations may applyone or more data compression algorithms. Compression may be applied increating a secondary copy 116 of a previously uncompressed secondarycopy, e.g., when making archive copies or disaster recovery copies. Theuse of compression may result in metadata that specifies the nature ofthe compression, so that data may be uncompressed on restore ifappropriate.

Data Analysis, Reporting, and Management Operations

Data analysis, reporting, and management operations can differ from datamovement operations in that they do not necessarily involve copying,migration or other transfer of data between different locations in thesystem. For instance, data analysis operations may involve processing(e.g., offline processing) or modification of already stored primarydata 112 and/or secondary copies 116. However, in some embodiments dataanalysis operations are performed in conjunction with data movementoperations. Some data analysis operations include content indexingoperations and classification operations which can be useful inleveraging data under management to enhance search and other features.

Classification Operations/Content Indexing

In some embodiments, information management system 100 analyzes andindexes characteristics, content, and metadata associated with primarydata 112 (“online content indexing”) and/or secondary copies 116(“off-line content indexing”). Content indexing can identify files orother data objects based on content (e.g., user-defined keywords orphrases, other keywords/phrases that are not defined by a user, etc.),and/or metadata (e.g., email metadata such as “to,” “from,” “cc,” “bcc,”attachment name, received time, etc.). Content indexes may be searchedand search results may be restored.

System 100 generally organizes and catalogues the results into a contentindex, which may be stored within media agent database 152, for example.The content index can also include the storage locations of or pointerreferences to indexed data in primary data 112 and/or secondary copies116. Results may also be stored elsewhere in system 100 (e.g., inprimary storage device 104 or in secondary storage device 108). Suchcontent index data provides storage manager 140 or other components withan efficient mechanism for locating primary data 112 and/or secondarycopies 116 of data objects that match particular criteria, thus greatlyincreasing the search speed capability of system 100. For instance,search criteria can be specified by a user through user interface 158 ofstorage manager 140. Moreover, when system 100 analyzes data and/ormetadata in secondary copies 116 to create an “off-line content index,”this operation has no significant impact on the performance of clientcomputing devices 102 and thus does not take a toll on the productionenvironment. Examples of content indexing techniques are provided inU.S. Pat. No. 8,170,995.

One or more components, such as a content index engine, can beconfigured to scan data and/or associated metadata for classificationpurposes to populate a database (or other data structure) ofinformation, which can be referred to as a “data classificationdatabase” or a “metabase.” Depending on the embodiment, the dataclassification database(s) can be organized in a variety of differentways, including centralization, logical sub-divisions, and/or physicalsub-divisions. For instance, one or more data classification databasesmay be associated with different subsystems or tiers within system 100.As an example, there may be a first metabase associated with primarystorage subsystem 117 and a second metabase associated with secondarystorage subsystem 118. In other cases, metabase(s) may be associatedwith individual components, e.g., client computing devices 102 and/ormedia agents 144. In some embodiments, a data classification databasemay reside as one or more data structures within management database146, may be otherwise associated with storage manager 140, and/or mayreside as a separate component. In some cases, metabase(s) may beincluded in separate database(s) and/or on separate storage device(s)from primary data 112 and/or secondary copies 116, such that operationsrelated to the metabase(s) do not significantly impact performance onother components of system 100. In other cases, metabase(s) may bestored along with primary data 112 and/or secondary copies 116. Files orother data objects can be associated with identifiers (e.g., tagentries, etc.) to facilitate searches of stored data objects. Among anumber of other benefits, the metabase can also allow efficient,automatic identification of files or other data objects to associatewith secondary copy or other information management operations. Forinstance, a metabase can dramatically improve the speed with whichsystem 100 can search through and identify data as compared to otherapproaches that involve scanning an entire file system. Examples ofmetabases and data classification operations are provided in U.S. Pat.Nos. 7,734,669 and 7,747,579.

Management and Reporting Operations

Certain embodiments leverage the integrated ubiquitous nature of system100 to provide useful system-wide management and reporting. Operationsmanagement can generally include monitoring and managing the health andperformance of system 100 by, without limitation, performing errortracking, generating granular storage/performance metrics (e.g., jobsuccess/failure information, deduplication efficiency, etc.), generatingstorage modeling and costing information, and the like. As an example,storage manager 140 or another component in system 100 may analyzetraffic patterns and suggest and/or automatically route data to minimizecongestion. In some embodiments, the system can generate predictionsrelating to storage operations or storage operation information. Suchpredictions, which may be based on a trending analysis, may predictvarious network operations or resource usage, such as network trafficlevels, storage media use, use of bandwidth of communication links, useof media agent components, etc. Further examples of traffic analysis,trend analysis, prediction generation, and the like are described inU.S. Pat. No. 7,343,453.

In some configurations having a hierarchy of storage operation cells, amaster storage manager 140 may track the status of subordinate cells,such as the status of jobs, system components, system resources, andother items, by communicating with storage managers 140 (or othercomponents) in the respective storage operation cells. Moreover, themaster storage manager 140 may also track status by receiving periodicstatus updates from the storage managers 140 (or other components) inthe respective cells regarding jobs, system components, systemresources, and other items. In some embodiments, a master storagemanager 140 may store status information and other information regardingits associated storage operation cells and other system information inits management database 146 and/or index 150 (or in another location).The master storage manager 140 or other component may also determinewhether certain storage-related or other criteria are satisfied, and mayperform an action or trigger event (e.g., data migration) in response tothe criteria being satisfied, such as where a storage threshold is metfor a particular volume, or where inadequate protection exists forcertain data. For instance, data from one or more storage operationcells is used to dynamically and automatically mitigate recognizedrisks, and/or to advise users of risks or suggest actions to mitigatethese risks. For example, an information management policy may specifycertain requirements (e.g., that a storage device should maintain acertain amount of free space, that secondary copies should occur at aparticular interval, that data should be aged and migrated to otherstorage after a particular period, that data on a secondary volumeshould always have a certain level of availability and be restorablewithin a given time period, that data on a secondary volume may bemirrored or otherwise migrated to a specified number of other volumes,etc.). If a risk condition or other criterion is triggered, the systemmay notify the user of these conditions and may suggest (orautomatically implement) a mitigation action to address the risk. Forexample, the system may indicate that data from a primary copy 112should be migrated to a secondary storage device 108 to free up space onprimary storage device 104. Examples of the use of risk factors andother triggering criteria are described in U.S. Pat. No. 7,343,453.

In some embodiments, system 100 may also determine whether a metric orother indication satisfies particular storage criteria sufficient toperform an action. For example, a storage policy or other definitionmight indicate that a storage manager 140 should initiate a particularaction if a storage metric or other indication drops below or otherwisefails to satisfy specified criteria such as a threshold of dataprotection. In some embodiments, risk factors may be quantified intocertain measurable service or risk levels. For example, certainapplications and associated data may be considered to be more importantrelative to other data and services. Financial compliance data, forexample, may be of greater importance than marketing materials, etc.Network administrators may assign priority values or “weights” tocertain data and/or applications corresponding to the relativeimportance. The level of compliance of secondary copy operationsspecified for these applications may also be assigned a certain value.Thus, the health, impact, and overall importance of a service may bedetermined, such as by measuring the compliance value and calculatingthe product of the priority value and the compliance value to determinethe “service level” and comparing it to certain operational thresholdsto determine whether it is acceptable. Further examples of the servicelevel determination are provided in U.S. Pat. No. 7,343,453.

System 100 may additionally calculate data costing and data availabilityassociated with information management operation cells. For instance,data received from a cell may be used in conjunction withhardware-related information and other information about system elementsto determine the cost of storage and/or the availability of particulardata. Exemplary information generated could include how fast aparticular department is using up available storage space, how long datawould take to recover over a particular pathway from a particularsecondary storage device, costs over time, etc. Moreover, in someembodiments, such information may be used to determine or predict theoverall cost associated with the storage of certain information. Thecost associated with hosting a certain application may be based, atleast in part, on the type of media on which the data resides, forexample. Storage devices may be assigned to a particular costcategories, for example. Further examples of costing techniques aredescribed in U.S. Pat. No. 7,343,453.

Any of the above types of information (e.g., information related totrending, predictions, job, cell or component status, risk, servicelevel, costing, etc.) can generally be provided to users via userinterface 158 in a single integrated view or console (not shown). Reporttypes may include: scheduling, event management, media management anddata aging. Available reports may also include backup history, dataaging history, auxiliary copy history, job history, library and drive,media in library, restore history, and storage policy, etc., withoutlimitation. Such reports may be specified and created at a certain pointin time as a system analysis, forecasting, or provisioning tool.Integrated reports may also be generated that illustrate storage andperformance metrics, risks and storage costing information. Moreover,users may create their own reports based on specific needs. Userinterface 158 can include an option to graphically depict the variouscomponents in the system using appropriate icons. As one example, userinterface 158 may provide a graphical depiction of primary storagedevices 104, secondary storage devices 108, data agents 142 and/or mediaagents 144, and their relationship to one another in system 100.

In general, the operations management functionality of system 100 canfacilitate planning and decision-making. For example, in someembodiments, a user may view the status of some or all jobs as well asthe status of each component of information management system 100. Usersmay then plan and make decisions based on this data. For instance, auser may view high-level information regarding secondary copy operationsfor system 100, such as job status, component status, resource status(e.g., communication pathways, etc.), and other information. The usermay also drill down or use other means to obtain more detailedinformation regarding a particular component, job, or the like. Furtherexamples are provided in U.S. Pat. No. 7,343,453.

System 100 can also be configured to perform system-wide e-discoveryoperations in some embodiments. In general, e-discovery operationsprovide a unified collection and search capability for data in thesystem, such as data stored in secondary storage devices 108 (e.g.,backups, archives, or other secondary copies 116). For example, system100 may construct and maintain a virtual repository for data stored insystem 100 that is integrated across source applications 110, differentstorage device types, etc. According to some embodiments, e-discoveryutilizes other techniques described herein, such as data classificationand/or content indexing.

Information Management Policies

An information management policy 148 can include a data structure orother information source that specifies a set of parameters (e.g.,criteria and rules) associated with secondary copy and/or otherinformation management operations.

One type of information management policy 148 is a “storage policy.”According to certain embodiments, a storage policy generally comprises adata structure or other information source that defines (or includesinformation sufficient to determine) a set of preferences or othercriteria for performing information management operations. Storagepolicies can include one or more of the following: (1) what data will beassociated with the storage policy, e.g., subclient; (2) a destinationto which the data will be stored; (3) datapath information specifyinghow the data will be communicated to the destination; (4) the type ofsecondary copy operation to be performed; and (5) retention informationspecifying how long the data will be retained at the destination (see,e.g., FIG. 1E). Data associated with a storage policy can be logicallyorganized into subclients, which may represent primary data 112 and/orsecondary copies 116. A subclient may represent static or dynamicassociations of portions of a data volume. Subclients may representmutually exclusive portions. Thus, in certain embodiments, a portion ofdata may be given a label and the association is stored as a staticentity in an index, database or other storage location. Subclients mayalso be used as an effective administrative scheme of organizing dataaccording to data type, department within the enterprise, storagepreferences, or the like. Depending on the configuration, subclients cancorrespond to files, folders, virtual machines, databases, etc. In oneexemplary scenario, an administrator may find it preferable to separatee-mail data from financial data using two different subclients.

A storage policy can define where data is stored by specifying a targetor destination storage device (or group of storage devices). Forinstance, where the secondary storage device 108 includes a group ofdisk libraries, the storage policy may specify a particular disk libraryfor storing the subclients associated with the policy. As anotherexample, where the secondary storage devices 108 include one or moretape libraries, the storage policy may specify a particular tape libraryfor storing the subclients associated with the storage policy, and mayalso specify a drive pool and a tape pool defining a group of tapedrives and a group of tapes, respectively, for use in storing thesubclient data. While information in the storage policy can bestatically assigned in some cases, some or all of the information in thestorage policy can also be dynamically determined based on criteria setforth in the storage policy. For instance, based on such criteria, aparticular destination storage device(s) or other parameter of thestorage policy may be determined based on characteristics associatedwith the data involved in a particular secondary copy operation, deviceavailability (e.g., availability of a secondary storage device 108 or amedia agent 144), network status and conditions (e.g., identifiedbottlenecks), user credentials, and the like.

Datapath information can also be included in the storage policy. Forinstance, the storage policy may specify network pathways and componentsto utilize when moving the data to the destination storage device(s). Insome embodiments, the storage policy specifies one or more media agents144 for conveying data associated with the storage policy between thesource and destination. A storage policy can also specify the type(s) ofassociated operations, such as backup, archive, snapshot, auxiliarycopy, or the like. Furthermore, retention parameters can specify howlong the resulting secondary copies 116 will be kept (e.g., a number ofdays, months, years, etc.), perhaps depending on organizational needsand/or compliance criteria.

When adding a new client computing device 102, administrators canmanually configure information management policies 148 and/or othersettings, e.g., via user interface 158. However, this can be an involvedprocess resulting in delays, and it may be desirable to begin dataprotection operations quickly, without awaiting human intervention.Thus, in some embodiments, system 100 automatically applies a defaultconfiguration to client computing device 102. As one example, when oneor more data agent(s) 142 are installed on a client computing device102, the installation script may register the client computing device102 with storage manager 140, which in turn applies the defaultconfiguration to the new client computing device 102. In this manner,data protection operations can begin substantially immediately. Thedefault configuration can include a default storage policy, for example,and can specify any appropriate information sufficient to begin dataprotection operations. This can include a type of data protectionoperation, scheduling information, a target secondary storage device108, data path information (e.g., a particular media agent 144), and thelike.

Another type of information management policy 148 is a “schedulingpolicy,” which specifies when and how often to perform operations.Scheduling parameters may specify with what frequency (e.g., hourly,weekly, daily, event-based, etc.) or under what triggering conditionssecondary copy or other information management operations are to takeplace. Scheduling policies in some cases are associated with particularcomponents, such as a subclient, client computing device 102, and thelike.

Another type of information management policy 148 is an “audit policy”(or “security policy”), which comprises preferences, rules and/orcriteria that protect sensitive data in system 100. For example, anaudit policy may define “sensitive objects” which are files or dataobjects that contain particular keywords (e.g., “confidential,” or“privileged”) and/or are associated with particular keywords (e.g., inmetadata) or particular flags (e.g., in metadata identifying a documentor email as personal, confidential, etc.). An audit policy may furtherspecify rules for handling sensitive objects. As an example, an auditpolicy may require that a reviewer approve the transfer of any sensitiveobjects to a cloud storage site, and that if approval is denied for aparticular sensitive object, the sensitive object should be transferredto a local primary storage device 104 instead. To facilitate thisapproval, the audit policy may further specify how a secondary storagecomputing device 106 or other system component should notify a reviewerthat a sensitive object is slated for transfer.

Another type of information management policy 148 is a “provisioningpolicy,” which can include preferences, priorities, rules, and/orcriteria that specify how client computing devices 102 (or groupsthereof) may utilize system resources, such as available storage oncloud storage and/or network bandwidth. A provisioning policy specifies,for example, data quotas for particular client computing devices 102(e.g., a number of gigabytes that can be stored monthly, quarterly orannually). Storage manager 140 or other components may enforce theprovisioning policy. For instance, media agents 144 may enforce thepolicy when transferring data to secondary storage devices 108. If aclient computing device 102 exceeds a quota, a budget for the clientcomputing device 102 (or associated department) may be adjustedaccordingly or an alert may trigger.

While the above types of information management policies 148 aredescribed as separate policies, one or more of these can be generallycombined into a single information management policy 148. For instance,a storage policy may also include or otherwise be associated with one ormore scheduling, audit, or provisioning policies or operationalparameters thereof. Moreover, while storage policies are typicallyassociated with moving and storing data, other policies may beassociated with other types of information management operations. Thefollowing is a non-exhaustive list of items that information managementpolicies 148 may specify:

-   -   schedules or other timing information, e.g., specifying when        and/or how often to perform information management operations;    -   the type of secondary copy 116 and/or copy format (e.g.,        snapshot, backup, archive, HSM, etc.);    -   a location or a class or quality of storage for storing        secondary copies 116 (e.g., one or more particular secondary        storage devices 108);    -   preferences regarding whether and how to encrypt, compress,        deduplicate, or otherwise modify or transform secondary copies        116;    -   which system components and/or network pathways (e.g., preferred        media agents 144) should be used to perform secondary storage        operations;    -   resource allocation among different computing devices or other        system components used in performing information management        operations (e.g., bandwidth allocation, available storage        capacity, etc.);    -   whether and how to synchronize or otherwise distribute files or        other data objects across multiple computing devices or hosted        services; and    -   retention information specifying the length of time primary data        112 and/or secondary copies 116 should be retained, e.g., in a        particular class or tier of storage devices, or within the        system 100.

Information management policies 148 can additionally specify or dependon historical or current criteria that may be used to determine whichrules to apply to a particular data object, system component, orinformation management operation, such as:

-   -   frequency with which primary data 112 or a secondary copy 116 of        a data object or metadata has been or is predicted to be used,        accessed, or modified;    -   time-related factors (e.g., aging information such as time since        the creation or modification of a data object);    -   deduplication information (e.g., hashes, data blocks,        deduplication block size, deduplication efficiency or other        metrics);    -   an estimated or historic usage or cost associated with different        components (e.g., with secondary storage devices 108);    -   the identity of users, applications 110, client computing        devices 102 and/or other computing devices that created,        accessed, modified, or otherwise utilized primary data 112 or        secondary copies 116;    -   a relative sensitivity (e.g., confidentiality, importance) of a        data object, e.g., as determined by its content and/or metadata;    -   the current or historical storage capacity of various storage        devices;    -   the current or historical network capacity of network pathways        connecting various components within the storage operation cell;    -   access control lists or other security information; and    -   the content of a particular data object (e.g., its textual        content) or of metadata associated with the data object.

Exemplary Storage Policy and Secondary Copy Operations

FIG. 1E includes a data flow diagram depicting performance of secondarycopy operations by an embodiment of information management system 100,according to an exemplary storage policy 148A. System 100 includes astorage manager 140, a client computing device 102 having a file systemdata agent 142A and an email data agent 142B operating thereon, aprimary storage device 104, two media agents 144A, 144B, and twosecondary storage devices 108: a disk library 108A and a tape library108B. As shown, primary storage device 104 includes primary data 112A,which is associated with a logical grouping of data associated with afile system (“file system subclient”), and primary data 112B, which is alogical grouping of data associated with email (“email subclient”). Thetechniques described with respect to FIG. 1E can be utilized inconjunction with data that is otherwise organized as well.

As indicated by the dashed box, the second media agent 144B and tapelibrary 108B are “off-site,” and may be remotely located from the othercomponents in system 100 (e.g., in a different city, office building,etc.). Indeed, “off-site” may refer to a magnetic tape located in remotestorage, which must be manually retrieved and loaded into a tape driveto be read. In this manner, information stored on the tape library 108Bmay provide protection in the event of a disaster or other failure atthe main site(s) where data is stored.

The file system subclient 112A in certain embodiments generallycomprises information generated by the file system and/or operatingsystem of client computing device 102, and can include, for example,file system data (e.g., regular files, file tables, mount points, etc.),operating system data (e.g., registries, event logs, etc.), and thelike. The e-mail subclient 112B can include data generated by an e-mailapplication operating on client computing device 102, e.g., mailboxinformation, folder information, emails, attachments, associateddatabase information, and the like. As described above, the subclientscan be logical containers, and the data included in the correspondingprimary data 112A and 112B may or may not be stored contiguously.

The exemplary storage policy 148A includes backup copy preferences orrule set 160, disaster recovery copy preferences or rule set 162, andcompliance copy preferences or rule set 164. Backup copy rule set 160specifies that it is associated with file system subclient 166 and emailsubclient 168. Each of subclients 166 and 168 are associated with theparticular client computing device 102. Backup copy rule set 160 furtherspecifies that the backup operation will be written to disk library 108Aand designates a particular media agent 144A to convey the data to disklibrary 108A. Finally, backup copy rule set 160 specifies that backupcopies created according to rule set 160 are scheduled to be generatedhourly and are to be retained for 30 days. In some other embodiments,scheduling information is not included in storage policy 148A and isinstead specified by a separate scheduling policy.

Disaster recovery copy rule set 162 is associated with the same twosubclients 166 and 168. However, disaster recovery copy rule set 162 isassociated with tape library 108B, unlike backup copy rule set 160.Moreover, disaster recovery copy rule set 162 specifies that a differentmedia agent, namely 144B, will convey data to tape library 108B.Disaster recovery copies created according to rule set 162 will beretained for 60 days and will be generated daily. Disaster recoverycopies generated according to disaster recovery copy rule set 162 canprovide protection in the event of a disaster or other catastrophic dataloss that would affect the backup copy 116A maintained on disk library108A.

Compliance copy rule set 164 is only associated with the email subclient168, and not the file system subclient 166. Compliance copies generatedaccording to compliance copy rule set 164 will therefore not includeprimary data 112A from the file system subclient 166. For instance, theorganization may be under an obligation to store and maintain copies ofemail data for a particular period of time (e.g., 10 years) to complywith state or federal regulations, while similar regulations do notapply to file system data. Compliance copy rule set 164 is associatedwith the same tape library 108B and media agent 144B as disasterrecovery copy rule set 162, although a different storage device or mediaagent could be used in other embodiments. Finally, compliance copy ruleset 164 specifies that the copies it governs will be generated quarterlyand retained for 10 years.

Secondary Copy Jobs

A logical grouping of secondary copy operations governed by a rule setand being initiated at a point in time may be referred to as a“secondary copy job” (and sometimes may be called a “backup job,” eventhough it is not necessarily limited to creating only backup copies).Secondary copy jobs may be initiated on demand as well. Steps 1-9 belowillustrate three secondary copy jobs based on storage policy 148A.

Referring to FIG. 1E, at step 1, storage manager 140 initiates a backupjob according to the backup copy rule set 160, which logically comprisesall the secondary copy operations necessary to effectuate rules 160 instorage policy 148A every hour, including steps 1-4 occurring hourly.For instance, a scheduling service running on storage manager 140accesses backup copy rule set 160 or a separate scheduling policyassociated with client computing device 102 and initiates a backup jobon an hourly basis. Thus, at the scheduled time, storage manager 140sends instructions to client computing device 102 (i.e., to both dataagent 142A and data agent 1428) to begin the backup job.

At step 2, file system data agent 142A and email data agent 142B onclient computing device 102 respond to instructions from storage manager140 by accessing and processing the respective subclient primary data112A and 112B involved in the backup copy operation, which can be foundin primary storage device 104. Because the secondary copy operation is abackup copy operation, the data agent(s) 142A, 142B may format the datainto a backup format or otherwise process the data suitable for a backupcopy.

At step 3, client computing device 102 communicates the processed filesystem data (e.g., using file system data agent 142A) and the processedemail data (e.g., using email data agent 142B) to the first media agent144A according to backup copy rule set 160, as directed by storagemanager 140. Storage manager 140 may further keep a record in managementdatabase 146 of the association between media agent 144A and one or moreof: client computing device 102, file system subclient 112A, file systemdata agent 142A, email subclient 112B, email data agent 142B, and/orbackup copy 116A.

The target media agent 144A receives the data-agent-processed data fromclient computing device 102, and at step 4 generates and conveys backupcopy 116A to disk library 108A to be stored as backup copy 116A, againat the direction of storage manager 140 and according to backup copyrule set 160. Media agent 144A can also update its index 153 to includedata and/or metadata related to backup copy 116A, such as informationindicating where the backup copy 116A resides on disk library 108A,where the email copy resides, where the file system copy resides, dataand metadata for cache retrieval, etc. Storage manager 140 may similarlyupdate its index 150 to include information relating to the secondarycopy operation, such as information relating to the type of operation, aphysical location associated with one or more copies created by theoperation, the time the operation was performed, status informationrelating to the operation, the components involved in the operation, andthe like. In some cases, storage manager 140 may update its index 150 toinclude some or all of the information stored in index 153 of mediaagent 144A. At this point, the backup job may be considered complete.After the 30-day retention period expires, storage manager 140 instructsmedia agent 144A to delete backup copy 116A from disk library 108A andindexes 150 and/or 153 are updated accordingly.

At step 5, storage manager 140 initiates another backup job for adisaster recovery copy according to the disaster recovery rule set 162.Illustratively this includes steps 5-7 occurring daily for creatingdisaster recovery copy 116B. Illustratively, and by way of illustratingthe scalable aspects and off-loading principles embedded in system 100,disaster recovery copy 1168 is based on backup copy 116A and not onprimary data 112A and 1128.

At step 6, illustratively based on instructions received from storagemanager 140 at step 5, the specified media agent 1448 retrieves the mostrecent backup copy 116A from disk library 108A.

At step 7, again at the direction of storage manager 140 and asspecified in disaster recovery copy rule set 162, media agent 144B usesthe retrieved data to create a disaster recovery copy 1168 and store itto tape library 1088. In some cases, disaster recovery copy 1168 is adirect, mirror copy of backup copy 116A, and remains in the backupformat. In other embodiments, disaster recovery copy 1168 may be furthercompressed or encrypted, or may be generated in some other manner, suchas by using primary data 112A and 1128 from primary storage device 104as sources. The disaster recovery copy operation is initiated once a dayand disaster recovery copies 1168 are deleted after 60 days; indexes 153and/or 150 are updated accordingly when/after each informationmanagement operation is executed and/or completed. The present backupjob may be considered completed.

At step 8, storage manager 140 initiates another backup job according tocompliance rule set 164, which performs steps 8-9 quarterly to createcompliance copy 116C. For instance, storage manager 140 instructs mediaagent 144B to create compliance copy 116C on tape library 1088, asspecified in the compliance copy rule set 164.

At step 9 in the example, compliance copy 116C is generated usingdisaster recovery copy 1168 as the source. This is efficient, becausedisaster recovery copy resides on the same secondary storage device andthus no network resources are required to move the data. In otherembodiments, compliance copy 116C is instead generated using primarydata 1128 corresponding to the email subclient or using backup copy 116Afrom disk library 108A as source data. As specified in the illustratedexample, compliance copies 116C are created quarterly, and are deletedafter ten years, and indexes 153 and/or 150 are kept up-to-dateaccordingly.

Exemplary Applications of Storage Policies—Information GovernancePolicies and Classification

Again referring to FIG. 1E, storage manager 140 may permit a user tospecify aspects of storage policy 148A. For example, the storage policycan be modified to include information governance policies to define howdata should be managed in order to comply with a certain regulation orbusiness objective. The various policies may be stored, for example, inmanagement database 146. An information governance policy may align withone or more compliance tasks that are imposed by regulations or businessrequirements. Examples of information governance policies might includea Sarbanes-Oxley policy, a HIPAA policy, an electronic discovery(e-discovery) policy, and so on.

Information governance policies allow administrators to obtain differentperspectives on an organization's online and offline data, without theneed for a dedicated data silo created solely for each differentviewpoint. As described previously, the data storage systems hereinbuild an index that reflects the contents of a distributed data set thatspans numerous clients and storage devices, including both primary dataand secondary copies, and online and offline copies. An organization mayapply multiple information governance policies in a top-down manner overthat unified data set and indexing schema in order to view andmanipulate the data set through different lenses, each of which isadapted to a particular compliance or business goal. Thus, for example,by applying an e-discovery policy and a Sarbanes-Oxley policy, twodifferent groups of users in an organization can conduct two verydifferent analyses of the same underlying physical set of data/copies,which may be distributed throughout the information management system.

An information governance policy may comprise a classification policy,which defines a taxonomy of classification terms or tags relevant to acompliance task and/or business objective. A classification policy mayalso associate a defined tag with a classification rule. Aclassification rule defines a particular combination of criteria, suchas users who have created, accessed or modified a document or dataobject; file or application types; content or metadata keywords; clientsor storage locations; dates of data creation and/or access; reviewstatus or other status within a workflow (e.g., reviewed orun-reviewed); modification times or types of modifications; and/or anyother data attributes in any combination, without limitation. Aclassification rule may also be defined using other classification tagsin the taxonomy. The various criteria used to define a classificationrule may be combined in any suitable fashion, for example, via Booleanoperators, to define a complex classification rule. As an example, ane-discovery classification policy might define a classification tag“privileged” that is associated with documents or data objects that (1)were created or modified by legal department staff, or (2) were sent toor received from outside counsel via email, or (3) contain one of thefollowing keywords: “privileged” or “attorney” or “counsel,” or otherlike terms. Accordingly, all these documents or data objects will beclassified as “privileged.”

One specific type of classification tag, which may be added to an indexat the time of indexing, is an “entity tag.” An entity tag may be, forexample, any content that matches a defined data mask format. Examplesof entity tags might include, e.g., social security numbers (e.g., anynumerical content matching the formatting mask XXX-XX-XXXX), credit cardnumbers (e.g., content having a 13-16 digit string of numbers), SKUnumbers, product numbers, etc. A user may define a classification policyby indicating criteria, parameters or descriptors of the policy via agraphical user interface, such as a form or page with fields to befilled in, pull-down menus or entries allowing one or more of severaloptions to be selected, buttons, sliders, hypertext links or other knownuser interface tools for receiving user input, etc. For example, a usermay define certain entity tags, such as a particular product number orproject ID. In some implementations, the classification policy can beimplemented using cloud-based techniques. For example, the storagedevices may be cloud storage devices, and the storage manager 140 mayexecute cloud service provider API over a network to classify datastored on cloud storage devices.

Restore Operations from Secondary Copies

While not shown in FIG. 1E, at some later point in time, a restoreoperation can be initiated involving one or more of secondary copies116A, 1168, and 116C. A restore operation logically takes a selectedsecondary copy 116, reverses the effects of the secondary copy operationthat created it, and stores the restored data to primary storage where aclient computing device 102 may properly access it as primary data. Amedia agent 144 and an appropriate data agent 142 (e.g., executing onthe client computing device 102) perform the tasks needed to complete arestore operation. For example, data that was encrypted, compressed,and/or deduplicated in the creation of secondary copy 116 will becorrespondingly rehydrated (reversing deduplication), uncompressed, andunencrypted into a format appropriate to primary data. Metadata storedwithin or associated with the secondary copy 116 may be used during therestore operation. In general, restored data should be indistinguishablefrom other primary data 112. Preferably, the restored data has fullyregained the native format that may make it immediately usable byapplication 110.

As one example, a user may manually initiate a restore of backup copy116A, e.g., by interacting with user interface 158 of storage manager140 or with a web-based console with access to system 100. Storagemanager 140 may accesses data in its index 150 and/or managementdatabase 146 (and/or the respective storage policy 148A) associated withthe selected backup copy 116A to identify the appropriate media agent144A and/or secondary storage device 108A where the secondary copyresides. The user may be presented with a representation (e.g., stub,thumbnail, listing, etc.) and metadata about the selected secondarycopy, in order to determine whether this is the appropriate copy to berestored, e.g., date that the original primary data was created. Storagemanager 140 will then instruct media agent 144A and an appropriate dataagent 142 on the target client computing device 102 to restore secondarycopy 116A to primary storage device 104. A media agent may be selectedfor use in the restore operation based on a load balancing algorithm, anavailability based algorithm, or other criteria. The selected mediaagent, e.g., 144A, retrieves secondary copy 116A from disk library 108A.For instance, media agent 144A may access its index 153 to identify alocation of backup copy 116A on disk library 108A, or may accesslocation information residing on disk library 108A itself.

In some cases a backup copy 116A that was recently created or accessed,may be cached to speed up the restore operation. In such a case, mediaagent 144A accesses a cached version of backup copy 116A residing inindex 153, without having to access disk library 108A for some or all ofthe data. Once it has retrieved backup copy 116A, the media agent 144Acommunicates the data to the requesting client computing device 102.Upon receipt, file system data agent 142A and email data agent 142B mayunpack (e.g., restore from a backup format to the native applicationformat) the data in backup copy 116A and restore the unpackaged data toprimary storage device 104. In general, secondary copies 116 may berestored to the same volume or folder in primary storage device 104 fromwhich the secondary copy was derived; to another storage location orclient computing device 102; to shared storage, etc. In some cases, thedata may be restored so that it may be used by an application 110 of adifferent version/vintage from the application that created the originalprimary data 112.

Exemplary Secondary Copy Formatting

The formatting and structure of secondary copies 116 can vary dependingon the embodiment. In some cases, secondary copies 116 are formatted asa series of logical data units or “chunks” (e.g., 512 MB, 1 GB, 2 GB, 4GB, or 8 GB chunks). This can facilitate efficient communication andwriting to secondary storage devices 108, e.g., according to resourceavailability. For example, a single secondary copy 116 may be written ona chunk-by-chunk basis to one or more secondary storage devices 108. Insome cases, users can select different chunk sizes, e.g., to improvethroughput to tape storage devices. Generally, each chunk can include aheader and a payload. The payload can include files (or other dataunits) or subsets thereof included in the chunk, whereas the chunkheader generally includes metadata relating to the chunk, some or all ofwhich may be derived from the payload. For example, during a secondarycopy operation, media agent 144, storage manager 140, or other componentmay divide files into chunks and generate headers for each chunk byprocessing the files. Headers can include a variety of information suchas file and/or volume identifier(s), offset(s), and/or other informationassociated with the payload data items, a chunk sequence number, etc.Importantly, in addition to being stored with secondary copy 116 onsecondary storage device 108, chunk headers can also be stored to index153 of the associated media agent(s) 144 and/or to index 150 associatedwith storage manager 140. This can be useful for providing fasterprocessing of secondary copies 116 during browsing, restores, or otheroperations. In some cases, once a chunk is successfully transferred to asecondary storage device 108, the secondary storage device 108 returnsan indication of receipt, e.g., to media agent 144 and/or storagemanager 140, which may update their respective indexes 153, 150accordingly. During restore, chunks may be processed (e.g., by mediaagent 144) according to the information in the chunk header toreassemble the files.

Data can also be communicated within system 100 in data channels thatconnect client computing devices 102 to secondary storage devices 108.These data channels can be referred to as “data streams,” and multipledata streams can be employed to parallelize an information managementoperation, improving data transfer rate, among other advantages. Exampledata formatting techniques including techniques involving datastreaming, chunking, and the use of other data structures in creatingsecondary copies are described in U.S. Pat. Nos. 7,315,923, 8,156,086,and 8,578,120.

FIGS. 1F and 1G are diagrams of example data streams 170 and 171,respectively, which may be employed for performing informationmanagement operations. Referring to FIG. 1F, data agent 142 forms datastream 170 from source data associated with a client computing device102 (e.g., primary data 112). Data stream 170 is composed of multiplepairs of stream header 172 and stream data (or stream payload) 174. Datastreams 170 and 171 shown in the illustrated example are for asingle-instanced storage operation, and a stream payload 174 thereforemay include both single-instance (SI) data and/or non-SI data. A streamheader 172 includes metadata about the stream payload 174. This metadatamay include, for example, a length of the stream payload 174, anindication of whether the stream payload 174 is encrypted, an indicationof whether the stream payload 174 is compressed, an archive fileidentifier (ID), an indication of whether the stream payload 174 issingle instanceable, and an indication of whether the stream payload 174is a start of a block of data.

Referring to FIG. 1G, data stream 171 has the stream header 172 andstream payload 174 aligned into multiple data blocks. In this example,the data blocks are of size 64 KB. The first two stream header 172 andstream payload 174 pairs comprise a first data block of size 64 KB. Thefirst stream header 172 indicates that the length of the succeedingstream payload 174 is 63 KB and that it is the start of a data block.The next stream header 172 indicates that the succeeding stream payload174 has a length of 1 KB and that it is not the start of a new datablock. Immediately following stream payload 174 is a pair comprising anidentifier header 176 and identifier data 178. The identifier header 176includes an indication that the succeeding identifier data 178 includesthe identifier for the immediately previous data block. The identifierdata 178 includes the identifier that the data agent 142 generated forthe data block. The data stream 171 also includes other stream header172 and stream payload 174 pairs, which may be for SI data and/or non-SIdata.

FIG. 1H is a diagram illustrating data structures 180 that may be usedto store blocks of SI data and non-SI data on a storage device (e.g.,secondary storage device 108). According to certain embodiments, datastructures 180 do not form part of a native file system of the storagedevice. Data structures 180 include one or more volume folders 182, oneor more chunk folders 184/185 within the volume folder 182, and multiplefiles within chunk folder 184. Each chunk folder 184/185 includes ametadata file 186/187, a metadata index file 188/189, one or morecontainer files 190/191/193, and a container index file 192/194.Metadata file 186/187 stores non-SI data blocks as well as links to SIdata blocks stored in container files. Metadata index file 188/189stores an index to the data in the metadata file 186/187. Containerfiles 190/191/193 store SI data blocks. Container index file 192/194stores an index to container files 190/191/193. Among other things,container index file 192/194 stores an indication of whether acorresponding block in a container file 190/191/193 is referred to by alink in a metadata file 186/187. For example, data block B2 in thecontainer file 190 is referred to by a link in metadata file 187 inchunk folder 185. Accordingly, the corresponding index entry incontainer index file 192 indicates that data block B2 in container file190 is referred to. As another example, data block B1 in container file191 is referred to by a link in metadata file 187, and so thecorresponding index entry in container index file 192 indicates thatthis data block is referred to.

As an example, data structures 180 illustrated in FIG. 1H may have beencreated as a result of separate secondary copy operations involving twoclient computing devices 102. For example, a first secondary copyoperation on a first client computing device 102 could result in thecreation of the first chunk folder 184, and a second secondary copyoperation on a second client computing device 102 could result in thecreation of the second chunk folder 185. Container files 190/191 in thefirst chunk folder 184 would contain the blocks of SI data of the firstclient computing device 102. If the two client computing devices 102have substantially similar data, the second secondary copy operation onthe data of the second client computing device 102 would result in mediaagent 144 storing primarily links to the data blocks of the first clientcomputing device 102 that are already stored in the container files190/191. Accordingly, while a first secondary copy operation may resultin storing nearly all of the data subject to the operation, subsequentsecondary storage operations involving similar data may result insubstantial data storage space savings, because links to already storeddata blocks can be stored instead of additional instances of datablocks.

If the operating system of the secondary storage computing device 106 onwhich media agent 144 operates supports sparse files, then when mediaagent 144 creates container files 190/191/193, it can create them assparse files. A sparse file is a type of file that may include emptyspace (e.g., a sparse file may have real data within it, such as at thebeginning of the file and/or at the end of the file, but may also haveempty space in it that is not storing actual data, such as a contiguousrange of bytes all having a value of zero). Having container files190/191/193 be sparse files allows media agent 144 to free up space incontainer files 190/191/193 when blocks of data in container files190/191/193 no longer need to be stored on the storage devices. In someexamples, media agent 144 creates a new container file 190/191/193 whena container file 190/191/193 either includes 100 blocks of data or whenthe size of the container file 190 exceeds 50 MB. In other examples,media agent 144 creates a new container file 190/191/193 when acontainer file 190/191/193 satisfies other criteria (e.g., it containsfrom approx. 100 to approx. 1000 blocks or when its size exceedsapproximately 50 MB to 1 GB). In some cases, a file on which a secondarycopy operation is performed may comprise a large number of data blocks.For example, a 100 MB file may comprise 400 data blocks of size 256 KB.If such a file is to be stored, its data blocks may span more than onecontainer file, or even more than one chunk folder. As another example,a database file of 20 GB may comprise over 40,000 data blocks of size512 KB. If such a database file is to be stored, its data blocks willlikely span multiple container files, multiple chunk folders, andpotentially multiple volume folders. Restoring such files may requireaccessing multiple container files, chunk folders, and/or volume foldersto obtain the requisite data blocks.

Using Backup Data for Replication and Disaster Recovery (“LiveSynchronization”)

There is an increased demand to off-load resource intensive informationmanagement tasks (e.g., data replication tasks) away from productiondevices (e.g., physical or virtual client computing devices) in order tomaximize production efficiency. At the same time, enterprises expectaccess to readily-available up-to-date recovery copies in the event offailure, with little or no production downtime.

FIG. 2A illustrates a system 200 configured to address these and otherissues by using backup or other secondary copy data to synchronize asource subsystem 201 (e.g., a production site) with a destinationsubsystem 203 (e.g., a failover site). Such a technique can be referredto as “live synchronization” and/or “live synchronization replication.”In the illustrated embodiment, the source client computing devices 202 ainclude one or more virtual machines (or “VMs”) executing on one or morecorresponding VM host computers 205 a, though the source need not bevirtualized. The destination site 203 may be at a location that isremote from the production site 201, or may be located in the same datacenter, without limitation. One or more of the production site 201 anddestination site 203 may reside at data centers at known geographiclocations, or alternatively may operate “in the cloud.”

The synchronization can be achieved by generally applying an ongoingstream of incremental backups from the source subsystem 201 to thedestination subsystem 203, such as according to what can be referred toas an “incremental forever” approach. FIG. 2A illustrates an embodimentof a data flow which may be orchestrated at the direction of one or morestorage managers (not shown). At step 1, the source data agent(s) 242 aand source media agent(s) 244 a work together to write backup or othersecondary copies of the primary data generated by the source clientcomputing devices 202 a into the source secondary storage device(s) 208a. At step 2, the backup/secondary copies are retrieved by the sourcemedia agent(s) 244 a from secondary storage. At step 3, source mediaagent(s) 244 a communicate the backup/secondary copies across a networkto the destination media agent(s) 244 b in destination subsystem 203.

As shown, the data can be copied from source to destination in anincremental fashion, such that only changed blocks are transmitted, andin some cases multiple incremental backups are consolidated at thesource so that only the most current changed blocks are transmitted toand applied at the destination. An example of live synchronization ofvirtual machines using the “incremental forever” approach is found inU.S. Patent Application No. 62/265,339 entitled “Live Synchronizationand Management of Virtual Machines across Computing and VirtualizationPlatforms and Using Live Synchronization to Support Disaster Recovery.”Moreover, a deduplicated copy can be employed to further reduce networktraffic from source to destination. For instance, the system can utilizethe deduplicated copy techniques described in U.S. Pat. No. 9,239,687,entitled “Systems and Methods for Retaining and Using Data BlockSignatures in Data Protection Operations.”

At step 4, destination media agent(s) 244 b write the receivedbackup/secondary copy data to the destination secondary storagedevice(s) 208 b. At step 5, the synchronization is completed when thedestination media agent(s) and destination data agent(s) 242 b restorethe backup/secondary copy data to the destination client computingdevice(s) 202 b. The destination client computing device(s) 202 b may bekept “warm” awaiting activation in case failure is detected at thesource. This synchronization/replication process can incorporate thetechniques described in U.S. patent application Ser. No. 14/721,971,entitled “Replication Using Deduplicated Secondary Copy Data.”

Where the incremental backups are applied on a frequent, on-going basis,the synchronized copies can be viewed as mirror or replication copies.Moreover, by applying the incremental backups to the destination site203 using backup or other secondary copy data, the production site 201is not burdened with the synchronization operations. Because thedestination site 203 can be maintained in a synchronized “warm” state,the downtime for switching over from the production site 201 to thedestination site 203 is substantially less than with a typical restorefrom secondary storage. Thus, the production site 201 may flexibly andefficiently fail over, with minimal downtime and with relativelyup-to-date data, to a destination site 203, such as a cloud-basedfailover site. The destination site 203 can later be reversesynchronized back to the production site 201, such as after repairs havebeen implemented or after the failure has passed.

Integrating with the Cloud Using File System Protocols

Given the ubiquity of cloud computing, it can be increasingly useful toprovide data protection and other information management services in ascalable, transparent, and highly plug-able fashion. FIG. 2B illustratesan information management system 200 having an architecture thatprovides such advantages, and incorporates use of a standard file systemprotocol between primary and secondary storage subsystems 217, 218. Asshown, the use of the network file system (NFS) protocol (or any anotherappropriate file system protocol such as that of the Common InternetFile System (CIFS)) allows data agent 242 to be moved from the primarystorage subsystem 217 to the secondary storage subsystem 218. Forinstance, as indicated by the dashed box 206 around data agent 242 andmedia agent 244, data agent 242 can co-reside with media agent 244 onthe same server (e.g., a secondary storage computing device such ascomponent 106), or in some other location in secondary storage subsystem218.

Where NFS is used, for example, secondary storage subsystem 218allocates an NFS network path to the client computing device 202 or toone or more target applications 210 running on client computing device202. During a backup or other secondary copy operation, the clientcomputing device 202 mounts the designated NFS path and writes data tothat NFS path. The NFS path may be obtained from NFS path data 215stored locally at the client computing device 202, and which may be acopy of or otherwise derived from NFS path data 219 stored in thesecondary storage subsystem 218.

Write requests issued by client computing device(s) 202 are received bydata agent 242 in secondary storage subsystem 218, which translates therequests and works in conjunction with media agent 244 to process andwrite data to a secondary storage device(s) 208, thereby creating abackup or other secondary copy. Storage manager 240 can include apseudo-client manager 217, which coordinates the process by, among otherthings, communicating information relating to client computing device202 and application 210 (e.g., application type, client computing deviceidentifier, etc.) to data agent 242, obtaining appropriate NFS path datafrom the data agent 242 (e.g., NFS path information), and deliveringsuch data to client computing device 202.

Conversely, during a restore or recovery operation client computingdevice 202 reads from the designated NFS network path, and the readrequest is translated by data agent 242. The data agent 242 then workswith media agent 244 to retrieve, re-process (e.g., re-hydrate,decompress, decrypt), and forward the requested data to client computingdevice 202 using NFS.

By moving specialized software associated with system 200 such as dataagent 242 off the client computing devices 202, the illustrativearchitecture effectively decouples the client computing devices 202 fromthe installed components of system 200, improving both scalability andplug-ability of system 200. Indeed, the secondary storage subsystem 218in such environments can be treated simply as a read/write NFS targetfor primary storage subsystem 217, without the need for informationmanagement software to be installed on client computing devices 202. Asone example, an enterprise implementing a cloud production computingenvironment can add VM client computing devices 202 without installingand configuring specialized information management software on theseVMs. Rather, backups and restores are achieved transparently, where thenew VMs simply write to and read from the designated NFS path. Anexample of integrating with the cloud using file system protocols orso-called “infinite backup” using NFS share is found in U.S. PatentApplication No. 62/294,920, entitled “Data Protection Operations Basedon Network Path Information.” Examples of improved data restorationscenarios based on network-path information, including using storedbackups effectively as primary data sources, may be found in U.S. PatentApplication No. 62/297,057, entitled “Data Restoration Operations Basedon Network Path Information.”

Highly Scalable Managed Data Pool Architecture

Enterprises are seeing explosive data growth in recent years, often fromvarious applications running in geographically distributed locations.FIG. 2C shows a block diagram of an example of a highly scalable,managed data pool architecture useful in accommodating such data growth.The illustrated system 200, which may be referred to as a “web-scale”architecture according to certain embodiments, can be readilyincorporated into both open compute/storage and common-cloudarchitectures.

The illustrated system 200 includes a grid 245 of media agents 244logically organized into a control tier 231 and a secondary or storagetier 233. Media agents assigned to the storage tier 233 can beconfigured to manage a secondary storage pool 208 as a deduplicationstore, and be configured to receive client write and read requests fromthe primary storage subsystem 217, and direct those requests to thesecondary tier 233 for servicing. For instance, media agents CMA1-CMA3in the control tier 231 maintain and consult one or more deduplicationdatabases 247, which can include deduplication information (e.g., datablock hashes, data block links, file containers for deduplicated files,etc.) sufficient to read deduplicated files from secondary storage pool208 and write deduplicated files to secondary storage pool 208. Forinstance, system 200 can incorporate any of the deduplication systemsand methods shown and described in U.S. Pat. No. 9,020,900, entitled“Distributed Deduplicated Storage System,” and U.S. Pat. Pub. No.2014/0201170, entitled “High Availability Distributed DeduplicatedStorage System.”

Media agents SMA1-SMA6 assigned to the secondary tier 233 receive writeand read requests from media agents CMA1-CMA3 in control tier 231, andaccess secondary storage pool 208 to service those requests. Mediaagents CMA1-CMA3 in control tier 231 can also communicate with secondarystorage pool 208, and may execute read and write requests themselves(e.g., in response to requests from other control media agentsCMA1-CMA3) in addition to issuing requests to media agents in secondarytier 233. Moreover, while shown as separate from the secondary storagepool 208, deduplication database(s) 247 can in some cases reside instorage devices in secondary storage pool 208.

As shown, each of the media agents 244 (e.g., CMA1-CMA3, SMA1-SMA6,etc.) in grid 245 can be allocated a corresponding dedicated partition251A-251I, respectively, in secondary storage pool 208. Each partition251 can include a first portion 253 containing data associated with(e.g., stored by) media agent 244 corresponding to the respectivepartition 251. System 200 can also implement a desired level ofreplication, thereby providing redundancy in the event of a failure of amedia agent 244 in grid 245. Along these lines, each partition 251 canfurther include a second portion 255 storing one or more replicationcopies of the data associated with one or more other media agents 244 inthe grid.

System 200 can also be configured to allow for seamless addition ofmedia agents 244 to grid 245 via automatic configuration. As oneillustrative example, a storage manager (not shown) or other appropriatecomponent may determine that it is appropriate to add an additional nodeto control tier 231, and perform some or all of the following: (i)assess the capabilities of a newly added or otherwise availablecomputing device as satisfying a minimum criteria to be configured as orhosting a media agent in control tier 231; (ii) confirm that asufficient amount of the appropriate type of storage exists to supportan additional node in control tier 231 (e.g., enough disk drive capacityexists in storage pool 208 to support an additional deduplicationdatabase 247); (iii) install appropriate media agent software on thecomputing device and configure the computing device according to apre-determined template; (iv) establish a partition 251 in the storagepool 208 dedicated to the newly established media agent 244; and (v)build any appropriate data structures (e.g., an instance ofdeduplication database 247). An example of highly scalable managed datapool architecture or so-called web-scale architecture for storage anddata management is found in U.S. Patent Application No. 62/273,286entitled “Redundant and Robust Distributed Deduplication Data StorageSystem.”

The embodiments and components thereof disclosed in FIGS. 2A, 2B, and2C, as well as those in FIGS. 1A-1H, may be implemented in anycombination and permutation to satisfy data storage management andinformation management needs at one or more locations and/or datacenters.

Automatic Failover of a Storage Manager

An information management system may include multiple client computingdevices, storage managers, secondary storage computing devices,secondary storage devices, auxiliary storage computing devices,auxiliary storage devices, and other such devices. As the number ofclient computing devices increases within the information managementsystem, it becomes increasingly important that the storage managermanaging these client computing devices have a minimal amount ofdowntime. In the event that the storage manager should fail, a failovernode in communicatively coupled to the storage manager may activate, andthe failover node may select another storage manager to assume theduties and responsibilities of the failed storage manager. This processmay be automated to reduce the recovery time objective (RTO) of theinformation management system. Furthermore, having multiple storagemanagers, which may be offline, synchronized to the active (or online)storage manager, ensures that the storage manager selected by thefailover node has a recent (or most recent) copy of the informationpreviously managed by the, now failed, storage manager.

FIG. 3A illustrates an information management system 302 configured toperform automatic failover of an active storage manager 308A, inaccordance with an example embodiment. The information management system302 may include multiple networks 304A-304C, where each network304A-304C represents a subnet 306A-306C or cluster 306A-306C of variouscomputing devices. In the example shown in FIG. 3A, the informationmanagement system 302 includes three networks 304A-304C, where eachnetwork 304A-304C represents a cluster 306A-306C of computing devices,and each cluster 306A-306C includes at least one storage manager308A-308C.

In one embodiment, the storage managers 308A-308C are implementedsimilarly to the storage manger 140 illustrated in FIG. 1C. Accordingly,the storage manager 308A-308C may include one or more componentsillustrated in FIG. 1C, such as a management database that stores one ormore information policies and/or an management index, a managementagent, a jobs agent, or any other components discussed with reference tothe storage manager 140. As discussed below with reference to FIG. 7 ,the storage managers 308A-308C may also include additional componentsthat facilitate the automatic failover of a storage manager.

A storage manager selected from the storage managers 308A-308C may bedesignated as the active storage manager. For example, the storagemanager 308A may be designated as the active storage manager. Thestorage manager 308A may be initially designated as the active storagemanager by an administrator or operator of the information managementsystem 302. The active storage manager 308 may be responsible forimplementing one or more information management policies and formanaging the primary data and/or secondary copies of the primary datawithin the information management system 302. Although shown in subnet306A, the active storage manager 308A may also communicate with one ormore of the other devices in the subnets 306B-306C, such as the storagemanager 308B, the storage manager 308C, the failover nodes 310B-310C,and the other computing devices.

In one embodiment, the active storage manager 308A backups and/orsynchronizes one or more of its databases (e.g., the managementdatabase) to one or more of the other, offline storage managers308B-308C. The active storage manager 308A may backup and/or synchronizeone or more of its databases based on an information management policy,according to a predetermined schedule stored by the active storagemanager 308A, and/or based on one or more predetermined conditions beingsatisfied. As one example, the active storage manager 308A may backupand/or synchronize its database with the other offline, storage managers308B-308C once an hour, once a day, every other day, or according to anyother schedule. In this regard, the active storage manager 308A isresponsible for implementing one or more information management policiesthat instruct the active storage manager 308A when to back up and/orsynchronize its one or more databases.

In another embodiment, one or more of the offline storage managers308B-308C back up and/or synchronize their management databases (notshown) with the management database of the active storage manager 308A.In this instance, an offline storage manager 308B-308C may be incommunication with the active storage manager 308A, but may not bedirecting the management of data for one or more client computingdevices and/or secondary storage devices. An offline storage manager308B-308C may retrieve data from one or more databases of the activestorage manager 308A, and synchronize that data with its own database.

The information management system 302 may also include one or morefailover nodes 310A-310C, where each failover node 310A-310C isassociated with a corresponding storage manager 308A-308C. Furthermore,the one or more offline storage managers 308B-308C may also becategorized as failover nodes as the offline storage managers 308B-308Care activated in response to the active storage manager 308A entering afailed state. In one embodiment, a failover node 310A-310C isimplemented similarly to a storage manager and/or a client computingdevice (e.g., having one or more processors, one or morecomputer-readable mediums, and so forth), but may also includeadditional components, applications, and/or data for facilitating theautomatic failover of the active storage manager 308A. Additionaldetails with regard to the components, applications, and/or data of afailover node 308A is further discussed with reference to FIG. 7 .

In general, a failover node 310A-310C is tasked with determining whetherto perform a failover of the active storage manager (e.g., activestorage manager 308A). Each storage manager 308A-308C may be associatedwith a corresponding failover node 310A-310C for redundancy to ensurethat at least one failover node 310A-310C can perform the failover ofthe active storage manager. To determine whether to perform a failover,a failover node may first determine whether the active storage manager308A is reachable (e.g., whether the active storage manager responds toone or more communications from the failover node). Where the failovernode determines that the active storage manager 308A is not reachable,the failover node may then use or execute one or more failover rules todetermine whether the active storage manager 308A is reachable and/orunavailable.

In determining whether the active storage manager 308A is unreachable,the failover node 310A may rely on the availability status of otherdevices in the information management system 302. The availabilitystatus of other devices in the information management system 302 may beused as a signal to the failover node 310A as to whether the storagemanager 308A is unreachable by other devices or is simply unreachable bythe failover node 310A. In one embodiment, selected devices of theinformation management 302 are designated as monitoring nodes, whereeach monitoring node is configured to communicate with each othermonitoring node.

FIG. 3B illustrates the information management system 302 of FIG. 3A,where one or more devices have been designated as monitoring nodes, inaccordance with an example embodiment. In one embodiment, an operatorand/or administrator of the information management system 302 selectsdevices from among the devices of the information management system 302to be monitoring nodes. The active storage manager 308A may maintain adatabase table (or other data structure) that identifies which of thedevices have been designated as a monitoring node. The monitoring nodesmay include any of the storage managers 308A-308C, any of the failovernodes 310A-310C, and one or more of the client computing devicesselected from the subnets or clusters 306A-306C. The client computingdevices that have been selected as monitoring nodes are illustrated withshading to distinguish from those client computing devices that have notbeen selected as monitoring nodes. To clarify, the first subnet orcluster 306A includes five monitoring nodes (e.g., three clientcomputing devices, the active storage manager 308A, and the failovernode 3010A), the second subnet or cluster 306B includes four monitoringnodes (e.g., two client computing devices, the offline storage manager308B, and the failover node 310B), and the third subnet or cluster 306Cincludes four monitoring nodes (e.g., two client computing devices, theoffline storage manager 308C, and the failover node 310C).

When a device is designated as a monitoring node, the active storagemanager 308A may communicate a configuration file to the designateddevice that configures the designated device as a monitoring node. Theconfiguration file may include one or more computer-executableinstructions (e.g., one or more computer applications, scripts, etc.)that, when executed by the designated device, causes the designateddevice to instantiate a monitoring application or process that isconfigured to communicate with all other devices that been designated asmonitoring nodes within the information management system 302.Similarly, the configuration file may configure the designated device tolisten (e.g., via a process thread) for incoming messages from othermonitoring nodes, and to respond to the messages from the othermonitoring nodes. In one embodiment, a device configured as a monitoringnode instantiates a listening process or thread that listens forincoming messages from other monitoring nodes; when the listeningprocess or thread receives an incoming message from a monitoring node,the listening process or thread may communicate an acknowledgementmessage (e.g., an “ACK” message) to the monitoring node from which theincoming message originating. Where a response is received (e.g., an ACKmessage), the listening process or thread may update a data structurethat indicates that the monitoring node was available. As discussedbelow with reference to FIGS. 5-7 , a monitoring node may also send outother messages to other monitoring nodes about the status of othermonitoring nodes.

Referring to FIG. 4 is an illustration of communication pathways of aselected group of monitoring nodes illustrated in FIG. 3B, in accordancewith an example embodiment. In FIG. 4 , three client computing devices402-406 have been designated as monitoring nodes, and the active storagemanager 308A and its associated failover node 310A are also monitoringnodes. Each device designated as a monitoring node is configured tocommunicate messages to each other monitoring node. In one embodiment,each monitoring node instantiates a session handler, where the sessionhandler is an application and/or a process configured to send a statusinquiry message to every other monitoring node. The session handler maywait for an acknowledgment message from a monitoring node to which thestatus inquiry message has been sent, where the session handler may waitfor a predetermined time period for the acknowledgement message. Wherethe session handler receives the acknowledgement message, the sessionhandler may update a data structure that indicates that the monitoringnode to which the status inquiry message was sent is reachable and/oravailable. Where the session handler does not receive theacknowledgement message within the predetermined time period, thesession handler may update a data structure indicating that themonitoring node to whom the status inquiry message was sent is notreachable and/or not available.

Although FIG. 4 illustrates that each monitoring node 402-406communicates with every other monitoring node, the active storagemanager 308A, and the failover node 310A, each monitoring node 402-406may also communicate with every monitoring node, storage managers, andfailover nodes of other subnets and/or clusters. For example, eachmonitoring node 402-406 may communicate with other monitoring nodes inthe subnets and/or clusters 306B-306C. Furthermore, the monitoring nodesin the subnets and/or clusters 306A-306C may communicate with otherstorage managers and/or failover nodes, including the storage managers308B-308C and the failover nodes 310B-310C. In addition, each of thestorage managers 308A-308C and/or the failover nodes 310A-310C maycommunicate with other storage managers 308A-308C and/or failover nodes310A-310C. Thus, in one embodiment, a monitoring node may be a clientcomputing device, a storage manager, a failover node, and/or any otherdevice within the information management system 302, and everymonitoring node may be configured to communicate with all othermonitoring nodes, including monitoring nodes separated by subnets and/orclusters.

FIG. 5 illustrates a client computing device 502 of the informationmanagement system 302 of FIG. 3A, in accordance with an exampleembodiment. In one embodiment, the client computing device 502 includesone or more processor(s) 504, one or more communication interface(s)506, one or more computer-readable medium(s) 508. The one or morecomputer-readable medium(s) 508 may include one or more application(s)510 and data 512. The client computing device 502 may be designated as amonitoring node, such as monitoring node 402 illustrated in FIG. 4 .

The one or more processor(s) 504 may be any type of commerciallyavailable processor, such as processors available from the IntelCorporation, Advanced Micro Devices, Qualcomm, Texas Instruments, orother such processors. Further still, the one or more processor(s) 504may include one or more special-purpose processors, such as aField-Programmable Gate Array (FPGA) or an Application SpecificIntegrated Circuit (ASIC). The one or more processor(s) 504 may alsoinclude programmable logic or circuitry that is temporarily configuredby software to perform certain operations. Thus, once configured by suchsoftware, the one or more processor(s) 504 become specific machines (orspecific components of a machine) uniquely tailored to perform theconfigured functions and are no longer general-purpose processors.

The one or more communication interface(s) 506 are configured tofacilitate communications between the client computing device 502 andother devices within the information management system 302, such asother monitoring nodes, the storage managers 308A-308C, and/or thefailover nodes 310A-310C. The one or more communication interface(s) 506may include wired communication components, wireless communicationcomponents, cellular communication components, Near Field Communication(NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy),Wi-Fi® components, and other communication components to providecommunication via other modalities.

The client computing device 502 further includes one or morecomputer-readable medium(s) 508 that store one or more application(s)510 and data 512 for monitoring and/or reporting the status of othermonitoring nodes. The computer-readable medium(s) 508 may include one ormore devices configured to store instructions and data temporarily orpermanently and may include, but is not be limited to, random-accessmemory (RAM), read-only memory (ROM), buffer memory, flash memory,optical media, magnetic media, cache memory, other types of storage(e.g., Erasable Programmable Read-Only Memory (EEPROM)) and/or anysuitable combination thereof. The term “computer-readable medium” shouldbe taken to include a single medium or multiple media (e.g., acentralized or distributed database, or associated caches and servers)able to store the application(s) 510 and the data 512. Accordingly, thecomputer-readable medium(s) 508 may be implemented as a single storageapparatus or device, or, alternatively and/or additionally, as a“cloud-based” storage systems or storage networks that include multiplestorage apparatus or devices.

In one embodiment, the application(s) 510 are written in acomputer-programming and/or scripting language. Examples of suchlanguages include, but are not limited to, C, C++, C#, Java, JavaScript,Perl, Python, or any other computer programming and/or scriptinglanguage now known or later developed.

The client computing device 502 may include a variety of software suchas an operating system, a web browser, a word processing application, ane-mail client, and so forth. A discussion of this software has beenomitted for brevity. To explain the benefits provided by the disclosedsystems and methods for performing an automatic failover of a storagemanager, FIG. 5 illustrates that the client computing device 502 mayinclude application(s) 510, which may include a session handler 514, adata agent 516, and a periodic thread 518.

The data agent 516 may be implemented similarly to the data agent 142discussed with reference to FIG. 1D. More particularly, the data agent516 be responsible for backing up primary data 522 which, as explainedpreviously, may be an initial or first stored body of data generated bya source (e.g., the client computing device 502). The primary data 522may be created substantially directly from data generated by acorresponding source application and may include files, directories,file system volumes, data blocks, extents, or any other hierarchies ororganizations of data objects. The data agent 516 may back up theprimary data 522 to one or more secondary storage devices (not shown) ofthe information management system 302.

The session handler 514 is configured to instantiate one or moreperiodic threads 518, and to manage the monitoring node statusesobtained from communicating the status inquiry message to one or more ofthe other monitoring nodes. The session handler 514 may instantiate apredetermined number of periodic threads 518, where each periodic thread518 is configured to communicate with one or more of the othermonitoring nodes. In addition, the session handler 514 may be taskedwith maintaining and/or updating a data structure that includes one ormore of the node statuses 520 based on whether a monitoring noderesponds to the status inquiry message communicated by the sessionhandler 514.

In one embodiment, the session handler 514 communicates a status inquirymessage to one or more of the designated monitoring nodes. A monitoringnode may be configured to reply and/or send an acknowledgment message inresponse to the status inquiry message. Where a reply and/or anacknowledgment is received from a designated monitoring node, thesession handler 514 may update a data structure that associates thedesignated monitoring nodes with their statuses 520. A node status maybe a binary value, where the node status is selected from valuescorresponding to “available” or “not available.” As one example, anumerical value of “1” may indicate that a monitoring node repliedand/or sent an acknowledgment message in response to the status inquirymessage (e.g., the monitoring node is reachable and/or available), and anumerical value of “0” may indicate that a monitoring node did not replyand/or send an acknowledgement message (e.g., the monitoring node is notreachable and/or not available). The session handler 514 may record amonitoring node status as not being reachable and/or not available wherethe session handler 514 does not receive a reply and/or acknowledgmentmessage within a predetermined time period after sending the statusinquiry message to a corresponding monitoring node. The monitoring nodesto which the session handler 514 may send the status inquiry message mayinclude, but are not limited to, the monitoring nodes designated by anoperator and/or administrator of the information management system 302,the one or more storage managers 308A-308C (including any online and/oroffline storage managers), the one or more failover nodes 310A-310C, andany other nodes in the information management system 302.

In addition to the status inquiry messages, a monitoring node may beconfigured to send one or more session messages to other monitoringnodes. In one embodiment, the client computing device 502 instantiates aperiodic thread 518 configured to send a session message to each devicedesignated as a monitoring node, where the session message includes thenode statuses 520 obtained by the session handler 514. The periodicthread 518 may communicate the session message at predetermined timeintervals (e.g., every ten minutes, once an hour, etc.) and/or inresponse to updating the status of one or more of the monitoring nodes(e.g., an acknowledgment message has been received and/or a monitoringnode has been determined as being nonresponsive). The periodic thread518 may communicate the session message to each monitoring noderegardless of whether the monitoring node is actually available (e.g.,the periodic thread 518 may communicate the session message to amonitoring node that is offline). As explained previously, the periodicthread 518 may communicate the session messages to one or more of theclient computing devices that been designated as monitoring nodes (e.g.,the monitoring nodes shaded in FIG. 3B0, the one or more storagemanagers 308A-308C, and/or the one or more failover nodes 310A-310C. Thesession handler 514 may also communicate the status inquiry message toother monitoring nodes not specifically illustrated in FIG. 3A and/orFIG. 3B, but illustrated in any of the other figures, including one ormore secondary storage computing devices, auxiliary storage computingdevices, or any other computing device.

To configure the client computing device 502 as a monitoring node, theclient computing device 502 may be loaded with configuration data 524.The configuration data 524 may have instructions that configure theclient computing device 502 to operate as a monitoring node and mayinclude, among other things, instructions for obtaining and/ordownloading the session handler 514, instructions for implementing thesession handler 514, instructions for implementing the periodic thread518, instructions for acting when an acknowledgement message isreceived, instructions for acting when an acknowledgement message is notreceived, timing data for the session handler 514 and/or the periodicthread 518, and other such configuration information that instruct theclient computing device 502 to act as a monitoring node. Theconfiguration data 524 may also include a data structure (e.g., a list,array, matrix, etc.), that identifies the other monitoring nodes in theinformation management system 302 and how the client computing device502 may communicate with the other monitoring nodes (e.g., an InternetProtocol (IP) address, port number, login credentials, authorizationcredentials, etc.).

In one embodiment, active storage manager 308A communicates theconfiguration data 524 to the client computing device 502. The activestorage manager 308A may also communicate the configuration data 524 toone or more of the other devices in the information management system302 including, but not limited to, another storage manager (e.g.,offline storage managers 308B-308C), one or more of the failover nodes310A-310C, one or more secondary storage computing devices, one or moreauxiliary storage computing devices, or any other device in theinformation management system 302. The active storage manager 308A maycommunicate the configuration data 524 to the client computing device502 in response to the client computing device 502 being designated as amonitoring node. The active storage manager 308A may also communicatethe configuration data 524 to a device in the information managementsystem 302 based on an instruction received by an operator oradministrator interacting with the active storage manager 308A.

The configuration data may initially include a default or base set ofinstructions (e.g., timing intervals, destination nodes, actions to takein response to acknowledgement instructions, etc.), where the default orbase set of instructions are generic to the devices of the informationmanagement system 302. As discussed with reference to FIG. 6 , thestorage manager may include a generic set of configuration data that isthen modified to accommodate a specific device (e.g., a client computingdevice, a storage manager, a failover node, etc.). In the example shownin FIG. 5 , the configuration data 524 may be specific to the clientcomputing device 502 and provide instructions and/or configurationinformation for the client computing device 502 to communicate withand/or interact with other monitoring nodes.

The data 512 may also include a data structure for storing and/orassociating one or more node statuses 520 with corresponding monitoringnodes in the information management system 302. The node statuses 520may be communicated by the client computing device 502 to one or more ofthe other monitoring nodes via the periodic thread 518. In oneembodiment, the node statuses 520 identify whether a particularmonitoring node is available or unavailable. In another embodiment, thenode statuses 520 identify whether a particular node is available orunavailable for another monitoring node. In this other embodiment, thenode statuses 520 may be implemented using an N×N array, where N is thenumber of monitoring nodes (including client computing devices, storagemanagers, secondary storage computing devices, etc.), and theintersections in the N×N array indicate whether a first monitoring nodewas available and/or reachable by a second monitoring node. Themonitoring nodes may reach receive a session message to ensure that eachmonitoring node includes an up-to-date copy of the node statuses 520within the information management system 302 in the event that one ormore monitoring nodes become unavailable and/or unreachable.

FIG. 6 illustrates the active storage manager 308A of the informationmanagement system 302 of FIG. 3A, in accordance with an exampleembodiment. In one embodiment, the storage manager 308A includes one ormore processor(s) 604, and one or more communication interface(s) 606,and one or more computer-readable medium(s) 608. The one or morecomputer-readable medium(s) 608 may include one or more application(s)610 and data 612. As with the client computing device 502, the storagemanager 308A may be designated as a monitoring node. However, in someinstances, the storage manager 308A may automatically be designated as amonitoring node when the storage manager 308A is communicatively coupledwithin the information management system 302.

The active storage manager 308A may be implemented similarly to thestorage manager 140 illustrated in FIG. 1C. Accordingly, the activestorage manager 308A may include one or more of the components of thestorage manager 140 and implement similar functionalities. The activestorage manager 308A may also include a management database (not shown)similar to the management database 146 illustrated in FIG. 1C.Furthermore, the active storage manager 308A may include the components,applications, and data illustrated in FIG. 6 in furtherance of theautomatic failover mechanism discussed herein.

The one or more processor(s) 604 may be any type of commerciallyavailable processor, such as processors available from the IntelCorporation, Advanced Micro Devices, Qualcomm, Texas Instruments, orother such processors. Further still, the one or more processor(s) 604may include one or more special-purpose processors, such as aField-Programmable Gate Array (FPGA) or an Application SpecificIntegrated Circuit (ASIC). The one or more processor(s) 604 may alsoinclude programmable logic or circuitry that is temporarily configuredby software to perform certain operations. Thus, once configured by suchsoftware, the one or more processor(s) 604 become specific machines (orspecific components of a machine) uniquely tailored to perform theconfigured functions and are no longer general-purpose processors.

The one or more communication interface(s) 606 are configured tofacilitate communications between the storage manager 308A and otherdevices within the information management system 302, such as othermonitoring nodes, the other storage managers 308B-308C, and/or thefailover nodes 310A-310C. The one or more communication interface(s) 606may include wired communication components, wireless communicationcomponents, cellular communication components, Near Field Communication(NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy),Wi-Fi® components, and other communication components to providecommunication via other modalities.

The storage manager 308A further includes one or more computer-readablemedium(s) 608 that store one or more application(s) 610 and data 612 forconfiguring new devices in the information management system 302 asmonitoring nodes, for monitoring and/or reporting the status of othermonitoring nodes, and/or for synchronizing its management database withthe other storage managers 308B-308C. The computer-readable medium(s)608 may include one or more devices configured to store instructions anddata temporarily or permanently and may include, but is not be limitedto, random-access memory (RAM), read-only memory (ROM), buffer memory,flash memory, optical media, magnetic media, cache memory, other typesof storage (e.g., Erasable Programmable Read-Only Memory (EEPROM))and/or any suitable combination thereof. The term “computer-readablemedium” should be taken to include a single medium or multiple media(e.g., a centralized or distributed database, or associated caches andservers) able to store the application(s) 610 and the data 612.Accordingly, the computer-readable medium(s) 608 may be implemented as asingle storage apparatus or device, or, alternatively and/oradditionally, as a “cloud-based” storage systems or storage networksthat include multiple storage apparatus or devices.

In one embodiment, the application(s) 610 are written in acomputer-programming and/or scripting language. Examples of suchlanguages include, but are not limited to, C, C++, C#, Java, JavaScript,Perl, Python, or any other computer programming and/or scriptinglanguage now known or later developed.

In one embodiment, the application(s) 610 include a session handler 614,a database synchronization application 616, one or more periodic threads618, and a configuration application 620. The storage manager 308A mayinclude other applications and/or components as discussed with referenceto FIG. 1C, but these applications and/or components have been omittedfor brevity.

The session handler 614 may be implemented similarly to the sessionhandler 514 discussed with reference to the client computing device 502of FIG. 5 . Accordingly, the session handler 614 may be configured tosend one or more status inquiry messages to other monitoring nodeswithin the information management system 302, including those monitoringnodes that may be located at other subnets and/or clusters. Where areply and/or an acknowledgment is received from a designated monitoringnode, the session handler 614 may update a data structure thatassociates the designated monitoring nodes with their statuses 622. Themonitoring nodes to which the session handler 614 may send the statusinquiry message may include, but are not limited to, the monitoringnodes designated by an operator and/or administrator of the informationmanagement system 302, the offline storage managers 308B-308C, the oneor more failover nodes 310A-310C, and any other nodes in the informationmanagement system 302.

In addition, the session handler 614 may instantiate one or moreperiodic threads 618, and manage the monitoring node statuses 622obtained from communicating status inquiry messages to one or more ofthe other monitoring nodes. The one or more periodic threads 618 may beconfigured to communicate the monitoring node status 622 to othermonitoring nodes within the information management system 302 via one ormore session messages to the other monitoring nodes.

The database synchronization application 616 is configured tosynchronize one or more databases of the active storage manager 308Awith the other offline storage managers (e.g., storage managers308B-308C). In one embodiment, the database synchronization application616 determines differences between the one or more databases managed bythe offline storage managers 308B-308C and the one or more databasesmanaged by the active storage manager 308A. In this regard, the offlinestorage managers 308B-308C may mirror the active storage manager 308A,where the offline storage managers 308B-308C include a similar oridentical configuration as the active storage manager 308A. In comparingthe databases, the database synchronization application 616 maydetermine whether the offline databases include the same, or up-to-date,information as the active database (e.g., the management database 146).Where there are differences, the database synchronization application616 updates and/or modifies the offline databases with the up-to-dateinformation found in the active database. Thus, the offline databasesrepresent identical, or nearly identical, copies of the active database.

The database synchronization application 616 may synchronize the activedatabase with the offline database at periodic intervals, based on oneor more information management policies stored in a management database,and/or based on one or more predetermined conditions being satisfied.For example, the database synchronization application 616 maysynchronize the one or more databases of the active storage manager 308Aon a daily basis (e.g., at the expiration of a 24-hour time period),when a new client computing device is added to the informationmanagement system 302 (e.g., a predetermined condition being satisfied),or when instructed to do so by an information management policy (e.g.,the current day is a particular day established by the informationmanagement policy). By synchronizing its one or more databases with theother offline storage managers 308B-308C, the active storage manager308A ensures that one of the offline storage managers can be broughtonline in the event of a failure, and that the offline storage managerincludes the most recent information managed by the active storagemanager 308A.

The application(s) 610 also include one or more periodic threads 618,which may be instantiated by the session handler 614. The one or moreperiodic threads 618 may be similar to the one or more periodic threads518 instantiated by the client computing device 502 of FIG. 5 . In thisregard, the one or more periodic threads 618 may communicate one or moresession messages to one or more of the designated monitoring nodes,where the one or more session messages including the node statuses 622.

The active storage manager 308A (or any of the other storage managers308B-308C) may also include a configuration application 620 that sendsdevice-specific configuration data 626 for causing the destinationdevice to act as a monitoring node (in addition to performing its otherfunctionalities). The device-specific configuration data 626 may bereceived by a monitoring node (e.g., the client computing device 502) asthe configuration data 524. The device-specific configuration data 626may be implemented as an executable script, where the destination deviceexecutes the executable script upon receiving the executable script. Thedevice-specific configuration data 626 may be based on defaultconfiguration data 624, where the default configuration data 624 ismodifiable depending on the destination device to which thedevice-specific configuration data 626 is being sent.

For example, an operator, user, or administrator of the informationmanagement system 302 may interact with the active storage manager 308Avia a graphical user interface (e.g., a locally displayed graphical userinterface, a web application displaying a web interface provided by theactive storage manager 308A, etc.), and may select, via the graphicaluser interface, one or more devices in the information management system302 to be monitoring nodes. Based on this selection, the active storagemanager 308A may first generate device-specific configuration data 626from the default configuration data 624 for each of the monitoringnodes. For example, the active storage manager 308A may first generate alist of the devices in the information management system 302 that aremonitoring nodes, and this list may be incorporated into thedevice-specific configuration data 626.

Furthermore, different device types may modify the default configurationdata 624 differently. For example, the default configuration data 624may specify that a session handler is to send a status inquiry messageevery ten minutes. However, where the device being configured is aclient computing device, the default configuration data 624 may bemodified so that the session handler is to send a status inquiry messageevery hour. As another example, where the device being configured is afailover node, the default configuration data 624 may be modified sothat the session handler is to send a status inquiry message everyfifteen minutes. Other attributes or characteristics of the defaultconfiguration data 624 may also be modified, including the list ofmonitoring nodes to whom the status inquiry message is sent, thefrequency of the status inquiry message, the values indicating whether amonitoring node is reachable and/or available, and any other attributesand/or characteristics used to configure a device as a monitoring node.In this manner, the default configuration data 624 can be used tosupport a wide variety of device types, and different types of devicescan be added into the information management system 302 as monitoringnodes.

FIG. 7 illustrates a failover node 310A of the information managementsystem 302 of FIG. 3A, in accordance with an example embodiment.Although FIG. 7 illustrates that the failover node 310A is associatedwith the active storage manager 308A, one of ordinary skill in the artwill appreciate that the components, applications, and data illustratedin FIG. 7 may also apply to other failover nodes, such as the failovernodes 310B-310C.

In one embodiment, the failover node 310A includes one or moreprocessor(s) 704, one or more communication interface(s) 706, and one ormore computer-readable medium(s) 708. The one or more computer-readablemedium(s) 708 may include one or more application(s) 710 and data 712.As with the client computing device 502, the failover node 310A may bedesignated as a monitoring node. However, in some instances, thefailover node 310A may automatically be designated as a monitoring nodewhen the failover node 310A is communicatively coupled within theinformation management system 302.

The one or more processor(s) 704 may be any type of commerciallyavailable processor, such as processors available from the IntelCorporation, Advanced Micro Devices, Qualcomm, Texas Instruments, orother such processors. Further still, the one or more processor(s) 704may include one or more special-purpose processors, such as aField-Programmable Gate Array (FPGA) or an Application SpecificIntegrated Circuit (ASIC). The one or more processor(s) 704 may alsoinclude programmable logic or circuitry that is temporarily configuredby software to perform certain operations. Thus, once configured by suchsoftware, the one or more processor(s) 704 become specific machines (orspecific components of a machine) uniquely tailored to perform theconfigured functions and are no longer general-purpose processors.

The one or more communication interface(s) 706 are configured tofacilitate communications between the failover node 310A and otherdevices within the information management system 302, such as othermonitoring nodes, the other storage managers 308A-308C, and/or thefailover nodes 310B-310C. The one or more communication interface(s) 706may include wired communication components, wireless communicationcomponents, cellular communication components, Near Field Communication(NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy),Wi-Fi® components, and other communication components to providecommunication via other modalities.

The failover node 310A further includes one or more computer-readablemedium(s) 708 that store one or more application(s) 710 and data 712 fordetermining whether to perform a failover of the active storage manager308A. The computer-readable medium(s) 708 may include one or moredevices configured to store instructions and data temporarily orpermanently and may include, but is not be limited to, random-accessmemory (RAM), read-only memory (ROM), buffer memory, flash memory,optical media, magnetic media, cache memory, other types of storage(e.g., Erasable Programmable Read-Only Memory (EEPROM)) and/or anysuitable combination thereof. The term “computer-readable medium” shouldbe taken to include a single medium or multiple media (e.g., acentralized or distributed database, or associated caches and servers)able to store the application(s) 710 and the data 712. Accordingly, thecomputer-readable medium(s) 708 may be implemented as a single storageapparatus or device, or, alternatively and/or additionally, as a“cloud-based” storage systems or storage networks that include multiplestorage apparatus or devices.

In one embodiment, the application(s) 710 are written in acomputer-programming and/or scripting language. Examples of suchlanguages include, but are not limited to, C, C++, C#, Java, JavaScript,Perl, Python, or any other computer programming and/or scriptinglanguage now known or later developed.

In one embodiment, the application(s) 710 include a session handler 714,failover application 716, and one or more periodic thread(s) 718. Thefailover node 310A may include other applications or components found ina computing device, such as an operating system, display devices,human/machine interfaces (e.g., keyboard, mouse, etc.), and other suchapplications and/or components, and a discussion of these elements hasbeen omitted for brevity and readability.

The session handler 714 may be implemented similarly to the sessionhandler 514 discussed with reference to the client computing device 502of FIG. 5 . Accordingly, the session handler 714 may be configured tosend one or more status inquiry messages to other monitoring nodeswithin the information management system 302, including those monitoringnodes that may be located at other subnets and/or clusters. In addition,the session handler 714 may instantiate one or more periodic threads 718and manage the monitoring node statuses 720 obtained from communicatingstatus inquiry messages to one or more of the other monitoring nodes.

In one embodiment, the failover application 716 is configured toinitiate a failover of the active storage manager 308A to one or more ofthe offline storage managers 310B-310C. To perform the failover of theactive storage manager 308A, the failover application 716 may initiallydetermine whether the storage manager 308A has entered a failover state.If the failover application 716 determines that the active storagemanager 308A is in a failover state, then the failover application 716may then determine which of the offline storage managers 310B-310C tobring online (e.g., enter an active state) and replace the currentstorage manager 308A.

In determining whether the active storage manager 308A has entered afailover state, the failover application 716 may periodically analyzeand/or monitor the node statuses 720. The node statuses 720 may beobtained by the session handler 714, and the one or more periodicthreads 718 may communicate one or more session messages to one or moreof the designated monitoring nodes that include the node statuses 720.In one embodiment, the one or more periodic threads 718 may be similarto the one or more periodic threads 518 instantiated by the clientcomputing device 502 of FIG. 5 .

As the session handler 714 may send status inquiry messages tomonitoring nodes and the active storage manager 308A, the node statuses720 may include up-to-date information as to the status of the activestorage manager 308A (e.g., based on whether the session handler 714received an acknowledgement message from the active storage manager710A). The failover application 716 may be configured to monitor and/orthe analyze the node statuses 720 every ten minutes, every hour, every24 hours, or at any other time period. An operator and/or administratorof the information management system 302 may also modify the timeinterval at which the failover application 716 checks the node statuses720, such as by increasing or decreasing the time interval.

Where the failover application 716 initially determines that the nodestatus of the active storage manager 308A is unavailable (e.g., the nodestatus associated with the active storage manager 308A indicates thatthe active storage manager 308A is unavailable and/or unreachable), thefailover application 716 may then apply one or more failover rule(s) 724to the other node statuses 720 to determine whether the active storagemanager 308A is, in fact, unavailable and/or unreachable. In someinstances, the active storage manager 308A may not be responsive to thestatus inquiry messages of the failover node 310A. For example, theactive storage manager 308A may be delayed in responding to the failovernode 310A. Accordingly, the statuses of the node statuses 720 mayindicate whether other monitoring nodes are able to reach the activestorage manager 308A.

The failover rules 724 may specify and/or define when the active storagemanager 308A is unavailable and/or unreachable by other monitoring nodesin the information management system 302. For example, one failover rule724 may specify that the failover application 716 should first determinewhether the network and/or subnet on which the active storage manager308A is located is reachable by other monitoring nodes outside of thenetwork and/or subnet. To perform this determination, the failoverapplication 716 may analyze the responses of monitoring nodes within thesame cluster and/or subnet as the active storage manager 308A relativeto the status inquiry messages of monitoring nodes outside of thecluster and/or subnet of the active monitoring node 308A. As oneexample, the failover application 716 may analyze the responses ofmonitoring nodes within the first subnet 306A to status inquiry messagesof monitoring nodes within the second subnet 306B and/or within thethird subnet 306C. If a threshold number of the node statuses indicatethat the monitoring nodes within the first subnet 3006A were unavailableand/or unreachable (e.g., more than 50% of the monitoring nodes), thefirst rule may specify that failover application 716 should determinethat the subnet and/or cluster in which the active storage manager 308Ais located is unreachable and/or unavailable.

In another embodiment, one or more of the failover rule(s) 724 mayspecify that a subnet and/or cluster is network accessible when at leastone monitoring node within the subnet and/or cluster responds to astatus inquiry message. Accordingly, in this example, the failoverapplication 716 may determine that the first subnet 306A is networkaccessible when at least one monitoring node of the first subnet 306Aresponds to a status inquiry message sent by one of the monitoring nodeswithin the second subnet 306B and/or within the third subnet 306C.

In yet another embodiment, the failover rule(s) 724 may specify and/ordefine that the failover application 716 is to first attempt to contactthe active storage manager 308A a predetermined number of times. Eachtime the failover application 716 sends a status inquiry message to theactive storage manager 308A, the failover application 716 increases acounter (e.g., an attempt counter) that records the number of times thefailover application 716 has tried to contact the active storage manager308A. When the failover application 716 receives a response from theactive storage manager 308A (e.g., receives an acknowledgement message),the attempt counter is reset (e.g., returned to a zero value). Where theattempt counter meets or exceeds a threshold value, the failoverapplication 716 may determine that the active storage manager 308A isunreachable and/or non-responsive. The failover application 716 mayattempt to contact the active storage manager 308A any number of times,such as two, three, four, five, or any other number of times.

In a similar embodiment, the failover rule(s) 724 may specify that theperiodic thread(s) 718 should attempt to contact the active storagemanager 308A and then store any responses (e.g., an acknowledgmentmessage) as part of the node statuses 720, and the failover application716 may be configured to check the node statuses 720 to determinewhether a response was received from the active storage manager 308A inreply to the status inquiry message sent by the one or more periodicthread(s) 718. The failover rule(s) 724 may further specify that thefailover application 716 is to check the node statuses 720 after waitingfor a predetermined period of time, and to perform this check apredetermined number of times.

For example, the failover application 716 may be configured to check thenode statuses 720 every 10 minutes to determine whether the activestorage manager 308A is reachable and/or unavailable, and to performthis check three times. After the third time of determining that thenode statuses 720 indicate that the active storage manager 308A isunreachable and/or unavailable, the failover application 716 may thenproceed to enter a failover state and/or execute one or more of theother failover rule(s) 724. Determining that the active storage manager308A is unavailable and/or unreachable by the failover node 310A may bea first step in entering a failover state as there may be any number ofreasons why the active storage manager 308A is not responsive to thefailover node 310A. Unnecessarily entering a failover state may lead toloss of data, excessive downtimes, loss of communications, or any otherundesirable effects, so ensuring that the active storage manager 308Ais, in fact, unavailable and/or unreachable may be a preferable courseof action in implementing the failover rule(s) 724.

In addition to determining whether the active storage manager 308A isunavailable and/or unreachable by the failover node 310A, the failoverrule(s) 724 may specify that the failover node 310A is to determinewhether the active storage manager 308A is network accessible by othermonitoring nodes in the information management system 302. Accordingly,one or more of the failover rule(s) 724 may specify whether the activestorage manager 308A is network accessible and/or network inaccessible.For example, if a threshold number of monitoring nodes (including otherstorage managers and/or failover nodes) are unable to access and/orreach the active storage manager 308A, the failover rule(s) 724 mayspecify that the active storage manager 308A is inaccessible and/orunreachable. In one embodiment, the failover application 716 may performthis determination by referencing one or more of the node statuses 720and determine whether the node statuses 720 indicate whether monitoringnodes outside of the subnet and/or cluster of the active storage manager308A (e.g., monitoring nodes outside of the subnet and/or cluster 306A)have received an acknowledgment message from the active storage manager308A in response to their own status inquiry messages. To recall, for agiven monitoring node, that monitoring node may communicate a datastructure that includes node status information about other nodes towhich the given monitoring node sent a status inquiry message. Sinceeach monitoring node is communicating this data structure to each othermonitoring node, each monitoring node includes a set of node statuses720 for monitoring nodes that have been communicating with each other.Therefore, by analyzing responses in the node statuses 720 betweenmonitoring nodes that are outside the subnet 306A and monitoring nodesthat are inside the subnet 306A, the failover application 716 determineswhether the active storage manager 308A is network accessible.

The one or more failover rule(s) 724 may further specify that thefailover application 716 is to obtain consensus from the other failovernodes in the information management system 302 that the active storagemanager 308A is not network accessible. Accordingly, the failoverapplication 716 may send a message or instruction to the other failovernodes 310B-310C that the other failover nodes 310B-310C are to determinewhether the active storage manager 308A is network accessible. The otherfailover nodes 310B-310C may then perform one or more of the operationspreviously discussed in determining whether the active storage manager308A is network accessible. After the other failover nodes 310B-310Chave made their determinations, the other failover nodes 310B-310C maycommunicate their results to the failover node 310A. Where a consensus,majority, or other predetermined amount of failover nodes, confirm thatthe active storage manager is not network accessible, the failoverapplication 716 may then determine that the active storage manager 308Ais not network accessible. Where a consensus, majority, or otherpredetermined amount of failover nodes, confirm that the active storagemanager is network accessible, the failover application 716 may thendetermine that the active storage manager 308A is network accessible,and may halt the failover of the active storage manager.

Where the failover application 716 determines that the active storagemanager 308A is not responsive and/or not network accessible, failoverrule(s) 726 may specify that the failover application 716 is to enter afailover state. When the failover application 716 enters the failoverstate, the failover application 716 may determine which of the offlinestorage managers (e.g., offline storage managers 308B-308C) are toreplace the active storage manager 308A and to become the new, activestorage manager. In performing this determination, the failoverapplication 716 may reference and/or analyze one or more database syncstatuses 722. In one embodiment, the database sync statuses 722 includethe status of database synchronizations between the active storagemanager 308A and other storage managers (e.g., offline storage managers308B-308C). Each time the active storage manager 308A completes asynchronization with another storage manager, the active storage manager308A may send a message to the failover node 310A that updates thedatabase sync status 722 with updated synchronization information. Thesynchronization information may include, but is not limited to, thesource storage manager (e.g., the active storage manager 308A), thedestination storage manager (e.g., an offline storage manager308B-308C), the database involved in the synchronization, the time atwhich the synchronization started, the time at which the synchronizationcompleted, the amount of elapsed time in performing the synchronization,the date on which the synchronization started and/or ended, and othersuch database synchronization information and/or various combinationsthereof. Additionally, and/or alternatively, a target storage managermay send a message to the failover node 310A that informs the failovernode 310A of the database synchronization and updates the database syncstatuses 722. In a further embodiment, each storage manager may send adatabase synchronization message to their corresponding failover node(e.g., the offline storage manager 308B sends a database synchronizationmessage to its failover node 310B and the offline storage manager 308Csends a database synchronization message to its failover node 310C).

By referencing the database sync statuses 722, the failover node 310Aassociated with the non-responsive, active storage manager 308Adetermines which offline storage manager was most recently updated.Accordingly, in one embodiment, the failover node 310A selects a storagemanager with the most recent database sync status 722 to be the newactive storage manager. The failover node 310A may select the storagemanager with the most recent database sync status 722 to be the newactive storage manager because it is likely that this storage managerhas a most up-to-date copy of the databases managed by the previous,non-responsive storage manager 308A. In the event that there are two ormore storage managers that have database sync statuses 722 that areidentical, the failover application 310A may select the storage managerthat is listed first in the database sync statuses 722. In analternative embodiment, where there are two or more storage managersthat have database sync statuses 722 that are identical, the failoverapplication 716 may randomly select a storage manager to be the new,active storage manager.

After selecting a storage manager to be a new, active storage manager(e.g., now-active storage manager 308B), the active storage manager 308Bmay send a message to managed devices (e.g., devices in the varioussubnets 306A-306C) that the devices are to receive and/or followinstructions from the active storage manager 308B. The storage manager308B then performs the operations previously performed by thenow-offline storage manager 308A, and the failover node 3108 associatedwith the active storage manager 308B begins performing the operationspreviously performed by the failover node 310A. In this way, storagemanager 308B becomes the new, active storage manager for the informationmanagement system 302 where the failover node 310A determines that thestorage manager 308A has entered a failover state.

FIG. 8 illustrates a messaging diagram 802 for updating monitoring nodestatuses of the information management system 302 of FIG. 3A, inaccordance with an example embodiment. The messaging diagram 802 isdiscussed with reference to the active storage manager 308A, but themessaging diagram 802 may be implemented by other monitoring nodes inthe information management system 302, such as the monitoring nodes402-406 highlighted in FIG. 4 .

As shown in FIG. 8 , and in one embodiment, the session handler 614receives various messages from the other monitoring nodes within theinformation management system 302. These messages include, but are notlimited to, status inquiry messages, database synchronization messages,acknowledgment messages, session messages, and any other messagepreviously described. The session handler 614 may update one or morenode statuses (e.g., the node statuses 622 illustrated in FIG. 6 ), andmay propagate the node statuses to other monitoring nodes within theinformation management system 302 via one or more periodic threads 618.As explained above, the one or more periodic threads 618 may send thesession messages to other monitoring nodes, where the one or moreperiodic threads may be configured to repeatedly send the sessionmessages at predetermined time intervals.

FIG. 8 further illustrates that a failover process may be initiated byone or more of the failover nodes 310A-310C of the informationmanagement system 302. As discussed above, the failover process mayfirst include determining whether the active storage manager isavailable and/or reachable. Where the active storage manager is notavailable and/or reachable, the failover process may further includedetermining whether the active storage manager is network accessible.Where the active storage manager is not network accessible, a designatedfailover node (e.g., the failover node associated with the activestorage manager) may then determine that the active storage manager isin a failover state, and the designated failover node may then perform afailover of the active storage manager. As explained previously,performing the failover may include determining which of the offlinestorage managers has been most recently synchronized with the previousactive storage manager, and then assigning the determined offlinestorage manager as the new, active storage manager. Additional detailsregarding the failover process are discussed with reference to FIGS.9A-9B and FIGS. 10A-10B.

FIGS. 9A-9B illustrate a method 902, in accordance with an exampleembodiment, for updating node statuses within the information managementsystem 302 of FIG. 3A and determining whether to enter a failover stateof an active storage manager 308A. The method 902 may be implemented byone or more of the devices illustrated in FIGS. 3A-3B, and is discussedby way of reference thereto.

As an initial manner, each of the monitoring nodes in the informationmanagement system 302 may perform the method 902 (labeled as Operation904). The various branches off of Operation 904 may each be performedsimultaneously and/or in parallel. A first operation may includegenerating a session message by one or more of the periodic threads,where the session message may include one or more node statuses(Operation 906). In some instances, the session message may include zeroor NULL values for some of the node statuses, as not every monitoringnode will have a corresponding node status when the session messages arefirst communicated. After an initial set of status inquiry messages arecommunicated by the session handler to the various monitoring nodes, thenode statuses may include non-zero or non-NULL values for the nodestatuses. The session message is then communicated to one or more of themonitoring nodes in the information management system 302 (Operation908).

The session handler may then monitor for one or more acknowledgementmessages to the session message (Operation 910). The session handler maymonitor for the one or more acknowledgment messages for a predeterminedperiod of time (e.g., a timeout value). An acknowledgment from amonitoring node to the session message may indicate that the monitoringnode to which the session message was sent is reachable and/oraccessible. Accordingly, where an acknowledgement message is received(e.g., the “YES” branch of Operation 910), the session handler mayupdate the node status corresponding to the monitoring node thatcommunicated the acknowledgment as being reachable and/or accessible(Operation 914). Where an acknowledgment message is not received (e.g.,not received on or before the expiration of the timeout value), thesession handler may update the node statuses to indicate that themonitoring node that did not send the acknowledgment message is notavailable and/or not accessible (e.g., the “NO” branch of Operation912). The method 902 then returns to Operation 904 where the sessionhandler iteratively performs Operations 906-914. In addition, themonitoring node may periodically communicate status inquiry messages toinquire as to the status of other monitoring nodes, where anacknowledgement to the status inquiry message is used to update thecorresponding node status.

Simultaneously and/or in parallel, the monitoring node may also performOperations 916-930. At Operation 916, and in one embodiment, themonitoring node determines whether it is a failover node (Operation916). Where the monitoring node is not a failover node (e.g., the “NO”branch of Operation 916), the method 902 returns back to Operation 904.Where the monitoring node is a failover node (e.g., the “YES” branch ofOperation 916), the method 902 may proceed to Operation 918, where thegiven monitoring node determines whether the active storage manager(e.g., the active storage manager 308A) is accessible and/or reachable(e.g., determining whether the active storage manager 308A responds tostatus inquiry messages). With regard to Operation 916, the monitoringnode may be configured to skip Operation 916 where the monitoring nodeis a failover node and, thus, does not need to perform the determinationof whether it is a failover node. Furthermore, Operations 916-930 maynot be performed where the monitoring node is a device or componentother than a failover node (e.g., a client computing device, a secondarystorage computing device, and so forth).

The failover node may perform Operation 918 periodically atpredetermined time intervals (e.g., every 10 minutes, every 30 minutes,every hour, etc.), and the predetermined time intervals may beconfigured by an administrator and/or operator of the informationmanagement system 302.

As explained above, and in one embodiment, determining whether theactive storage manager (e.g., the active storage manager 308A), isaccessible and/or reachable may include sending a status inquiry messageto the active storage manager via the session handler 714. Should thefailover node not receive an acknowledgement message from the activestorage manager (e.g., on and/or after a predetermined time periodelapses), the failover node may determine that the active storagemanager is not reachable and/or accessible. In another embodiment,determining whether the active storage manager is accessible and/orreachable may include referencing the node statuses 720 and determiningwhether the node status corresponding to the active storage manager 308Aindicates that the active storage manager 308A is accessible and/orreachable. Where the failover node determines that the active storagemanager is reachable and/or accessible (e.g., the “YES” branch ofOperation 918), the method 902 may proceed to the “END” label, but oneof ordinary skill in the art will appreciate that Operations 916-918 maybe repeated by the failover node at predetermined time intervals. Wherethe failover node determines that the active storage manager is notreachable and/or accessible (e.g., the “NO” branch of Operation 918),the method 902 may proceed to Operation 920 on FIG. 9B.

At Operation 920, the failover node determines whether a predeterminedretry threshold has been reached in attempting to contact the activestorage manager (Operation 920). For example, the failover node may beconfigured to attempt to contact the active storage manager three timeswhere, after the third attempt, the failover node proceeds to Operation922. A retry threshold may be established for the failover node because,in some instances, the active storage manager may be delayed inresponding or may be performing processes that detract from its abilityto effectively respond to status inquiry messages. Accordingly, it maybe preferable not to perform a failover simply because the activestorage manager is busy with other tasks; thus, having a retry thresholdensures that the failover is performed where there is a relatively highprobability that the active storage manager is, in fact, in a failoverstate and not unavailable due to other reasons.

Where the number of retries has not been reached (e.g., the “NO” branchof Operation 920), the failover part of the method 902 effectively ends,but the failover node may be configured to return to Operation 916and/or Operation 918 on FIG. 9A. Where the number of retries has beenreached (e.g., the “YES” branch of Operation 920), the method 902proceeds to Operation 922.

At Operation 922, the failover node determines whether the activestorage manager is network accessible. As explained previously, thefailover node may determined whether the active storage manager isnetwork accessible by analyzing the node statuses and applying one ormore failover rule(s) using the node statuses. The application of theone or more failover rule(s) may result in the failover node determiningwhether the active storage manager is or is not available. Where thefailover node determines that the active storage manager is not networkaccessible (e.g., the “NO” branch of Operation 922), the failover partof the method 902 effectively ends, but the failover node may beconfigured to return to Operation 916 and/or Operation 918 on FIG. 9A.Where the failover node determines that the active storage manager isnetwork accessible (e.g., the “YES” branch of Operation 922), the method902 proceeds to Operation 924.

At Operation 924, the failover node determines which of the offlinestorage managers should be used for failover (Operation 924). Asexplained above, the active storage manager may be synchronizing one ormore of its databases with the offline storage managers, and thenupdating a database sync status (e.g., the database sync status 722)managed by the failover node. The database sync status may includevarious synchronization information such as the source storage manager(e.g., the active storage manager 308A), the destination storage manager(e.g., an offline storage manager 308B-308C), the database involved inthe synchronization, the time at which the synchronization started, thetime at which the synchronization completed, the amount of elapsed timein performing the synchronization, the date on which the synchronizationstarted and/or ended, and other such database synchronizationinformation and/or various combinations thereof. By reference thedatabase sync status, the failover node determines which of the offlinestorage managers was most recently synchronized with the active storagemanager.

The failover node may then determine whether the selected offlinestorage manager should be used for the failover of the active storagemanager (Operation 926). In one embodiment, the failover node mayperform this determination by communicating a status inquiry message tothe offline storage manager to confirm that the offline storage manageris network accessible. Additionally, and/or alternatively, the failovernode may reference the node statuses (e.g., the node statuses 720) todetermine the last known node status of the selected offline storagemanager. Should the node status indicate that the offline storagemanager is not reachable and/or not accessible, then the failover nodemay determine that the selected storage manager should not be used forfailover (e.g., the “NO” branch of Operation 926). Where the failovernode determines that the selected storage manager should not be used forfailover, the method 902 may return to Operation 924, where the failovernode then selects a different, offline storage manager for failover.Alternatively, where the failover node determines that the offlinestorage manager is reachable and/or accessible (e.g., the “YES” branchof Operation 926), the failover node may instruct the offline storagemanager to activate (Operation 928).

At Operation 928, the selected, offline storage manager activates andbecomes the new, active storage manager. In this regard, the new, activestorage manager may inform the other nodes in the information managementsystem 302 that the other nodes should accept directions and/orinstructions from the new, active storage manager (Operation 930). Thenew, active storage manager then assumes the duties and responsibilitiesof the previous, active storage manager. In this fashion, the method 902implements a failover process that occurs automatically, ensures minimaldowntime of a storage manager, and reduces the potential for data losswithin the information management system 302.

FIGS. 10A-10B illustrate a method 1002, in accordance with an exampleembodiment, for activating a failover node of the information managementsystem 302 illustrated in FIG. 3A. The method 1002 may be implemented byone or more of the devices illustrated in FIGS. 3A-7 and is discussed byway of reference thereto. In addition, one or more of the operationsdiscussed with reference to FIGS. 10A-10B may also be implementedadditionally and/or alternatively to one or more of the operations ofthe method 902 discussed with reference to FIGS. 9A-9B.

Referring initially to FIG. 10A, a failover node may instantiate afailover application (e.g., failover application 716) for performing afailover of an active storage manager within the information managementsystem 302 (Operation 1004). As explained with reference to FIG. 7 , thefailover application 716 may be configured to determine whether theactive storage manager has entered a failover state and, if so, toperform a failover of the active storage manager.

At Operation 1006, the failover node may receive one or more sessionmessages from other monitoring nodes in the information managementsystem 302 (Operation 1006). The one or more session messages mayinclude node status information for one or more of the nodes within theinformation management system 302. The session handler 714 may updateone or more node statuses 720 based on the node status informationcontained within the session message (Operation 1008). As explainedpreviously, the node status information may indicate whether the activestorage manager is responsive to the failover node and/or to othermonitoring nodes within the information management system 302. Thefailover application 716 may then apply one or more of the failoverrule(s) 724 to the node statuses 720 (Operation 1010).

At Operation 1012, the failover application 716 determines whether thereis a failover condition based on result of applying the one or morefailover rule(s) 724 (Operation 1012). In determining whether a failovercondition exists, the failover application 716 may determine whether theactive storage manager (e.g., active storage manager 308A) is reachableand/or accessible and, if not, whether the active storage manager isnetwork reachable and/or accessible. Furthermore, the failoverapplication 716 may request that other failover nodes in the informationmanagement system 302 determine whether the actives storage manager isnetwork accessible and/or reachable.

Based on the application of the one or more failover rule(s) 724, thefailover application 716 determines whether the active storage manager308A has entered a failover state. Where the failover application 716determines that the active storage manager 308A has not entered afailover state (e.g., the “NO” branch of Operation 1012), the method1002 may return to Operation 1006). Alternatively, where the failoverapplication 716 determines that the active storage manager 308A hasentered a failover state (e.g., the “YES” branch of Operation 1012), themethod 1002 then proceeds to Operation 1014.

At Operation 1014, the failover node determines which of the offlinestorage managers should be used for failover (Operation 1014). Asexplained above, the active storage manager may be synchronizing one ormore of its databases with the offline storage managers, and thenupdating a database sync status (e.g., the database sync status 722)managed by the failover node. The database sync status may includevarious synchronization information such as the source storage manager(e.g., the active storage manager 308A), the destination storage manager(e.g., an offline storage manager 308B-308C), the database involved inthe synchronization, the time at which the synchronization started, thetime at which the synchronization completed, the amount of elapsed timein performing the synchronization, the date on which the synchronizationstarted and/or ended, and other such database synchronizationinformation and/or various combinations thereof. By reference thedatabase sync status, the failover node determines which of the offlinestorage managers was most recently synchronized with the active storagemanager. The failover node then selects the offline storage manager thathas been most recently synchronized with the active storage manager tobe the new, active storage manager (Operation 1016).

At Operation 1018, the selected, offline storage manager activates andbecomes the new, active storage manager. In this regard, the new, activestorage manager may inform the other nodes in the information managementsystem 302 that the other nodes should accept directions and/orinstructions from the new, active storage manager (Operation 1020). Thenew, active storage manager then assumes the duties and responsibilitiesof the previous, active storage manager. In this fashion, the method1002 implements a failover process that occurs automatically, ensuresminimal downtime of a storage manager, and reduces the potential fordata loss within the information management system 302.

In this manner, the foregoing description provides an informationmanagement system that implements an automatic failover of a storagemanager and leverages distributed computing techniques to determinewhether the storage manager has actually failed and, if so, whichpotential offline storage manager should assume the duties of the failedstorage manager. By using monitoring nodes distributed across variousnetworks and/or subnets, a designated failover node can determinewhether an active storage manager has entered a failover state and isnon-responsive to any monitoring node, or whether the active storagemanager is simply non-responsive to a particular monitoring node orfailover node. The systems, methods, techniques, and operationsdisclosed herein provide a technological advancement in the field ofdata backup and recovery operations. These techniques ensure thatpotential downtime of a computing system is minimized and that apotential failed state of an active storage manager is an actual failedstate, and not merely a false positive.

Example Embodiments

Some example enumerated embodiments of the present invention are recitedin this section in the form of methods, systems, and non-transitorycomputer-readable media, without limitation. In one embodiment, thisdisclosure provides a method for determining whether to initiate afailover of a storage manager in an information management system, themethod comprising assigning selected nodes of a plurality of nodes in aninformation management system as monitoring nodes to obtain a pluralityof monitoring nodes, wherein the plurality of nodes is configured tocommunicate with a first storage manager of the information managementsystem, and each monitoring node is configured to transmit a statusmessage to each other monitoring node. The method also includesreceiving, at a monitoring node, a plurality of status messages, whereineach status message was transmitted by another monitoring node of theassigned plurality of monitoring nodes, and generating, at themonitoring node, a session message comprising status information foreach monitoring node of the assigned plurality of monitoring nodes,wherein the status information is obtained from the received pluralityof status messages. The method further includes transmitting the sessionmessage to a plurality of failover nodes and determining, by at leastone failover node of the plurality of failover nodes, whether a failovercondition has occurred by applying a plurality of failover rules to thestatus information of the transmitted session message. The methodadditionally includes activating a failover node selected from theplurality of failover nodes to be a second storage manager based on adetermination that the failover condition has occurred, and instructing,by the activated second storage manager, that the plurality ofmonitoring nodes is to communicate with the activated second storagemanager instead of the first storage manager, wherein the activatedsecond storage manager performs the functionalities of the first storagemanager in the information management system.

In another embodiment of the method, the monitoring node instantiates asession handler configured to process the received plurality of statusmessages, and update a time and status for each monitoring nodeassociated with a corresponding status message of the plurality ofstatus messages.

In a further embodiment of the method, the status information comprisestime and status for each monitoring node of the assigned plurality ofmonitoring nodes.

In yet another embodiment of the method, the monitoring nodeinstantiates a periodic thread to transmit the session message, whereinthe periodic thread is configured to transmit the session message atpredetermined time intervals.

In yet a further embodiment of the method, each failover node isassociated with a corresponding database, wherein the correspondingdatabase is a backup of a database in communication with the firststorage manager, and the method further comprises selecting the at leastone failover node to activate based on which database of thecorresponding databases is the most recent backup of the database incommunication with the storage manager relative to the othercorresponding databases.

In another embodiment of the method, the method further comprisesverifying that the failover condition has occurred by requesting thateach failover node of the plurality of failover nodes confirm that thefailover condition has occurred.

In a further embodiment of the method, the method includes sending aconfiguration file to each selected node of the plurality of nodes thathave been selected to be monitoring nodes, and automatically configuringeach of the selected nodes to be a monitoring node based on the sentconfiguration file.

This disclosure also describes a system that determines whether toinitiate a failover of a storage manager in an information managementsystem, the system comprising one or more non-transitory,computer-readable mediums having computer-executable instructions storedthereon, and one or more processors that, having executed thecomputer-executable instructions, configure the system to perform aplurality of operations. The plurality of operations includes assigningselected nodes of a plurality of nodes in an information managementsystem as monitoring nodes to obtain a plurality of monitoring nodes,wherein the plurality of nodes is configured to communicate with a firststorage manager of the information management system, and eachmonitoring node is configured to transmit a status message to each othermonitoring node. The plurality of operations also includes receiving, ata monitoring node, a plurality of status messages, wherein each statusmessage was transmitted by another monitoring node of the assignedplurality of monitoring nodes. The plurality of operations furtherincludes generating, at the monitoring node, a session messagecomprising status information for each monitoring node of the assignedplurality of monitoring nodes, wherein the status information isobtained from the received plurality of status messages. The pluralityof operations additionally includes transmitting the session message toa plurality of failover nodes, and determining, by at least one failovernode of the plurality of failover nodes, whether a failover conditionhas occurred by applying a plurality of failover rules to the statusinformation of the transmitted session message. The plurality ofoperations also includes activating a failover node selected from theplurality of failover nodes to be a second storage manager based on adetermination that the failover condition has occurred, and instructing,by the activated second storage manager, that the plurality ofmonitoring nodes is to communicate with the activated second storagemanager instead of the first storage manager, wherein the activatedsecond storage manager performs the functionalities of the first storagemanager in the information management system.

In another embodiment of the system, the monitoring node instantiates asession handler configured to process the received plurality of statusmessages, and update a time and status for each monitoring nodeassociated with a corresponding status message of the plurality ofstatus messages.

In a further embodiment of the system, the status information comprisestime and status for each monitoring node of the assigned plurality ofmonitoring nodes.

In yet another embodiment of the system, the monitoring nodeinstantiates a periodic thread to transmit the session message, whereinthe periodic thread is configured to transmit the session message atpredetermined time intervals.

In yet a further embodiment of the system, each failover node isassociated with a corresponding database, wherein the correspondingdatabase is a backup of a database in communication with the firststorage manager, and the plurality of operations further comprisesselecting the at least one failover node to activate based on whichdatabase of the corresponding databases is the most recent backup of thedatabase in communication with the storage manager relative to the othercorresponding databases.

In another embodiment of the system, the plurality of operations furthercomprises verifying that the failover condition has occurred byrequesting that each failover node of the plurality of failover nodesconfirm that the failover condition has occurred.

In a further embodiment of the system, the plurality of operationsfurther comprises sending a configuration file to each selected node ofthe plurality of nodes that have been selected to be monitoring nodes,and automatically configuring each of the selected nodes to be amonitoring node based on the sent configuration file.

This disclosure further describes a non-transitory, computer-readablemedium having computer-executable instructions stored thereon that, whenexecuted by one or more processors, cause the one or more processors toperform a plurality of operations determining whether to initiate afailover of a storage manager in an information management system, theplurality of operations comprising assigning selected nodes of aplurality of nodes in an information management system as monitoringnodes to obtain a plurality of monitoring nodes, wherein the pluralityof nodes is configured to communicate with a first storage manager ofthe information management system, and each monitoring node isconfigured to transmit a status message to each other monitoring node.The plurality of operations further includes receiving, at a monitoringnode, a plurality of status messages, wherein each status message wastransmitted by another monitoring node of the assigned plurality ofmonitoring nodes, and generating, at the monitoring node, a sessionmessage comprising status information for each monitoring node of theassigned plurality of monitoring nodes, wherein the status informationis obtained from the received plurality of status messages. Theplurality of operations also includes transmitting the session messageto a plurality of failover nodes, and determining, by at least onefailover node of the plurality of failover nodes, whether a failovercondition has occurred by applying a plurality of failover rules to thestatus information of the transmitted session message. The plurality ofoperations additionally includes activating a failover node selectedfrom the plurality of failover nodes to be a second storage managerbased on a determination that the failover condition has occurred, andinstructing, by the activated second storage manager, that the pluralityof monitoring nodes is to communicate with the activated second storagemanager instead of the first storage manager, wherein the activatedsecond storage manager performs the functionalities of the first storagemanager in the information management system.

In another embodiment of the non-transitory, computer-readable medium,wherein the monitoring node instantiates a session handler configured toprocess the received plurality of status messages, and update a time andstatus for each monitoring node associated with a corresponding statusmessage of the plurality of status messages.

In a further embodiment of the non-transitory, computer-readable medium,the status information comprises time and status for each monitoringnode of the assigned plurality of monitoring nodes.

In yet another embodiment of the non-transitory, computer-readablemedium, the monitoring node instantiates a periodic thread to transmitthe session message, wherein the periodic thread is configured totransmit the session message at predetermined time intervals.

In yet a further embodiment of the non-transitory, computer-readablemedium, each failover node is associated with a corresponding database,wherein the corresponding database is a backup of a database incommunication with the first storage manager, and the plurality ofoperations further comprises selecting the at least one failover node toactivate based on which database of the corresponding databases is themost recent backup of the database in communication with the storagemanager relative to the other corresponding databases.

In another embodiment of the non-transitory, computer-readable medium,the plurality of operations further comprises verifying that thefailover condition has occurred by requesting that each failover node ofthe plurality of failover nodes confirm that the failover condition hasoccurred.

This disclosure also provides for a method for determining whether toinitiate a failover of a storage manager in an information managementsystem, the method comprising receiving, by a first failover node, asession message comprising status information for a plurality ofmonitoring nodes, wherein each monitoring node is configured to transmitstatus information to each other monitoring node, wherein the firstfailover node is a backup node for a storage manager that managesinformation storage policies for the information management system. Themethod may also include determining, by the first failover node, whethera failover condition has occurred by applying a plurality of failoverrules to the status information of the received session message. Themethod may further include verifying, by the first failover node, thatthe failover condition has occurred by requesting that a second failovernode confirm that the failover condition has occurred based on thereceived session message and activating the first failover node based onverification that the failover condition has occurred. The method mayalso include instructing, by the first failover node, each monitoringnode of the plurality of monitoring nodes to communicate with the firstfailover node instead of the storage manager, wherein the first failovernode performs the functionalities of the storage manager in theinformation management system.

This disclosure also provides for a system that determines whether toinitiate a failover of a storage manager in an information managementsystem, the system comprising one or more non-transitory,computer-readable mediums having computer-executable instructions storedthereon, and one or more processors that, having executed thecomputer-executable instructions, configure the system to perform aplurality of operations that include receiving, by a first failovernode, a session message comprising status information for a plurality ofmonitoring nodes, wherein each monitoring node is configured to transmitstatus information to each other monitoring node, wherein the firstfailover node is a backup node for a storage manager that managesinformation storage policies for the information management system. Theplurality of operations may also include determining, by the firstfailover node, whether a failover condition has occurred by applying aplurality of failover rules to the status information of the receivedsession message. The plurality of operations may further includeverifying, by the first failover node, that the failover condition hasoccurred by requesting that a second failover node confirm that thefailover condition has occurred based on the received session messageand activating the first failover node based on verification that thefailover condition has occurred. The plurality of operations may alsoinclude instructing, by the first failover node, each monitoring node ofthe plurality of monitoring nodes to communicate with the first failovernode instead of the storage manager, wherein the first failover nodeperforms the functionalities of the storage manager in the informationmanagement system.

Terminology

Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainembodiments include, while other embodiments do not include, certainfeatures, elements and/or steps. Thus, such conditional language is notgenerally intended to imply that features, elements and/or steps are inany way required for one or more embodiments or that one or moreembodiments necessarily include logic for deciding, with or without userinput or prompting, whether these features, elements and/or steps areincluded or are to be performed in any particular embodiment.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense, as opposed to anexclusive or exhaustive sense, i.e., in the sense of “including, but notlimited to.” As used herein, the terms “connected,” “coupled,” or anyvariant thereof means any connection or coupling, either direct orindirect, between two or more elements; the coupling or connectionbetween the elements can be physical, logical, or a combination thereof.Additionally, the words “herein,” “above,” “below,” and words of similarimport, when used in this application, refer to this application as awhole and not to any particular portions of this application. Where thecontext permits, words using the singular or plural number may alsoinclude the plural or singular number respectively. The word “or” inreference to a list of two or more items, covers all of the followinginterpretations of the word: any one of the items in the list, all ofthe items in the list, and any combination of the items in the list.Likewise the term “and/or” in reference to a list of two or more items,covers all of the following interpretations of the word: any one of theitems in the list, all of the items in the list, and any combination ofthe items in the list.

In some embodiments, certain operations, acts, events, or functions ofany of the algorithms described herein can be performed in a differentsequence, can be added, merged, or left out altogether (e.g., not allare necessary for the practice of the algorithms). In certainembodiments, operations, acts, functions, or events can be performedconcurrently, e.g., through multi-threaded processing, interruptprocessing, or multiple processors or processor cores or on otherparallel architectures, rather than sequentially.

Systems and modules described herein may comprise software, firmware,hardware, or any combination(s) of software, firmware, or hardwaresuitable for the purposes described. Software and other modules mayreside and execute on servers, workstations, personal computers,computerized tablets, PDAs, and other computing devices suitable for thepurposes described herein. Software and other modules may be accessiblevia local computer memory, via a network, via a browser, or via othermeans suitable for the purposes described herein. Data structuresdescribed herein may comprise computer files, variables, programmingarrays, programming structures, or any electronic information storageschemes or methods, or any combinations thereof, suitable for thepurposes described herein. User interface elements described herein maycomprise elements from graphical user interfaces, interactive voiceresponse, command line interfaces, and other suitable interfaces.

Further, processing of the various components of the illustrated systemscan be distributed across multiple machines, networks, and othercomputing resources. Two or more components of a system can be combinedinto fewer components. Various components of the illustrated systems canbe implemented in one or more virtual machines, rather than in dedicatedcomputer hardware systems and/or computing devices. Likewise, the datarepositories shown can represent physical and/or logical data storage,including, e.g., storage area networks or other distributed storagesystems. Moreover, in some embodiments the connections between thecomponents shown represent possible paths of data flow, rather thanactual connections between hardware. While some examples of possibleconnections are shown, any of the subset of the components shown cancommunicate with any other subset of components in variousimplementations.

Embodiments are also described above with reference to flow chartillustrations and/or block diagrams of methods, apparatus (systems) andcomputer program products. Each block of the flow chart illustrationsand/or block diagrams, and combinations of blocks in the flow chartillustrations and/or block diagrams, may be implemented by computerprogram instructions. Such instructions may be provided to a processorof a general purpose computer, special purpose computer,specially-equipped computer (e.g., comprising a high-performancedatabase server, a graphics subsystem, etc.) or other programmable dataprocessing apparatus to produce a machine, such that the instructions,which execute via the processor(s) of the computer or other programmabledata processing apparatus, create means for implementing the actsspecified in the flow chart and/or block diagram block or blocks. Thesecomputer program instructions may also be stored in a non-transitorycomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to operate in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meanswhich implement the acts specified in the flow chart and/or blockdiagram block or blocks. The computer program instructions may also beloaded to a computing device or other programmable data processingapparatus to cause operations to be performed on the computing device orother programmable apparatus to produce a computer implemented processsuch that the instructions which execute on the computing device orother programmable apparatus provide steps for implementing the actsspecified in the flow chart and/or block diagram block or blocks.

Any patents and applications and other references noted above, includingany that may be listed in accompanying filing papers, are incorporatedherein by reference. Aspects of the invention can be modified, ifnecessary, to employ the systems, functions, and concepts of the variousreferences described above to provide yet further implementations of theinvention. These and other changes can be made to the invention in lightof the above Detailed Description. While the above description describescertain examples of the invention, and describes the best modecontemplated, no matter how detailed the above appears in text, theinvention can be practiced in many ways. Details of the system may varyconsiderably in its specific implementation, while still beingencompassed by the invention disclosed herein. As noted above,particular terminology used when describing certain features or aspectsof the invention should not be taken to imply that the terminology isbeing redefined herein to be restricted to any specific characteristics,features, or aspects of the invention with which that terminology isassociated. In general, the terms used in the following claims shouldnot be construed to limit the invention to the specific examplesdisclosed in the specification, unless the above Detailed Descriptionsection explicitly defines such terms. Accordingly, the actual scope ofthe invention encompasses not only the disclosed examples, but also allequivalent ways of practicing or implementing the invention under theclaims.

To reduce the number of claims, certain aspects of the invention arepresented below in certain claim forms, but the applicant contemplatesother aspects of the invention in any number of claim forms. Forexample, while only one aspect of the invention is recited as ameans-plus-function claim under 35 U.S.C sec. 112(f) (AIA), otheraspects may likewise be embodied as a means-plus-function claim, or inother forms, such as being embodied in a computer-readable medium. Anyclaims intended to be treated under 35 U.S.C. § 112(f) will begin withthe words “means for,” but use of the term “for” in any other context isnot intended to invoke treatment under 35 U.S.C. § 112(f). Accordingly,the applicant reserves the right to pursue additional claims afterfiling this application, in either this application or in a continuingapplication.

What is claimed is:
 1. A method for determining whether to initiate afailover of a storage manager in an information management system, themethod comprising: assigning two or more nodes of a plurality ofcomputing nodes in an information management system as monitoring nodes,wherein: each of the monitoring nodes is configured to: communicate witha first storage manager, wherein the first storage manager initiatesdata protection operations according to an information management policyassigned to primary data generated by a plurality of client computingdevices, transmit a status message to each other monitoring node,receive a plurality of status messages, wherein each status message wastransmitted by another monitoring node, generate a session messagecomprising status information from the received plurality of statusmessages, and transmit the session message to a plurality of failovernodes; receiving at least one session message from a monitoring node;determining that a failover condition has occurred by applying aplurality of failover rules to the status information of the at leastone received session message; and in response to determining that thefailover condition has occurred: assigning second storage manager from aplurality of storage managers to take place of the first storagemanager, and to perform functionalities of the first storage manager inthe information management system.
 2. The method of claim 1, wherein thesecond storage manager is in an offline state.
 3. The method of claim 1,wherein the second storage manager is a storage manager for anotherregion within the information management system.
 4. The method of claim1, wherein at least one computing node of the plurality of computingnodes is a secondary storage computing device.
 5. The method of claim 1,wherein at least one computing node of the plurality of computing nodesis a client computing device that generates at least some of the primarydata protected by the first storage manager.
 6. The method of claim 1,wherein the determining that the failover condition has occurred isperformed by at least one failover node of the plurality of failovernodes.
 7. The method of claim 1, wherein the monitoring nodeinstantiates a session handler configured to: process the receivedplurality of status messages, and update a time and status for eachmonitoring node associated with a corresponding status message of theplurality of status messages.
 8. The method of claim 7, wherein thestatus information comprises time and status for each monitoring node.9. The method of claim 1, wherein the monitoring node instantiates aperiodic thread to transmit the session message, wherein the periodicthread is configured to transmit the session message at predeterminedtime intervals.
 10. The method of claim 1, wherein: each failover nodeis associated with a corresponding database, wherein the correspondingdatabase is a backup of a database in communication with the firststorage manager, and the method further comprises selecting at least onefailover node to activate based on which database of the correspondingdatabases is most recent backup of the database in communication withthe storage manager relative to other corresponding databases.
 11. Themethod of claim 1, wherein the method further comprises: verifying thatthe failover condition has occurred by requesting that each failovernode of the plurality of failover nodes confirm that the failovercondition has occurred.
 12. The method of claim 1, further comprising:sending a configuration file to each selected node of the pluralitycomputing nodes that have been selected to be monitoring nodes; and,automatically configuring each of the selected nodes to be a monitoringnode based on the configuration file.
 13. A system that determineswhether to initiate a failover of a storage manager in an informationmanagement system, the system comprising: one or more processors that,having executed computer-executable instructions, configure the systemto perform a plurality of operations comprising: assigning two or morenodes of a plurality of computing nodes in an information managementsystem as monitoring nodes, wherein: each of the monitoring nodes isconfigured to: communicate with a first storage manager, wherein thefirst storage manager initiates data protection operations according toan information management policy assigned to primary data generated by aplurality of client computing devices, transmit a status message to eachother monitoring node, receive a plurality of status messages, whereineach status message was transmitted by another monitoring node, generatea session message comprising status information from the receivedplurality of status messages, and transmit the session message to aplurality of failover nodes; receiving at least one session message froma monitoring node; determining that a failover condition has occurred byapplying a plurality of failover rules to the status information of theat least one received session message; and in response to determiningthat the failover condition has occurred: assigning second storagemanager from a plurality of storage managers to take place of the firststorage manager, and to perform functionalities of the first storagemanager in the information management system.
 14. The system of claim13, wherein the second storage manager is a storage manager for anotherregion within the information management system.
 15. The system of claim13, wherein at least one computing node of the plurality of computingnodes is a secondary storage computing device.
 16. The system of claim13, wherein at least one computing node of the plurality of computingnodes is a client computing device that generates at least some of theprimary data protected by the first storage manager.
 17. The system ofclaim 13, wherein the monitoring node instantiates a session handlerconfigured to: process the received plurality of status messages, andupdate a time and status for each monitoring node associated with acorresponding status message of the plurality of status messages. 18.The system of claim 13, wherein the monitoring node instantiates aperiodic thread to transmit the session message, wherein the periodicthread is configured to transmit the session message at predeterminedtime intervals.
 19. The system of claim 13, wherein: each failover nodeis associated with a corresponding database, wherein the correspondingdatabase is a backup of a database in communication with the firststorage manager; and wherein the plurality of operations furthercomprises: selecting at least one failover node to activate based onwhich database of the corresponding databases is most recent backup ofthe database in communication with the storage manager relative to othercorresponding databases.
 20. The system of claim 13, wherein thedetermining that the failover condition has occurred is performed by atleast one failover node of the plurality of failover nodes; and whereinthe plurality of operations further comprises: verifying that thefailover condition has occurred by requesting that each failover node ofthe plurality of failover nodes confirm that the failover condition hasoccurred.
 21. The system of claim 13, wherein the plurality ofoperations further comprises: sending a configuration file to eachselected node of the plurality computing nodes that have been selectedto be monitoring nodes; and, automatically configuring each of theselected nodes to be a monitoring node based on the configuration file.